Wireless data storage chassis

ABSTRACT

Various embodiments are directed to a data storage chassis for storing a plurality of non-specific storage drives, corresponding wireless controllers, and one or more radio adapters. The storage drives are operative to communicate with another network device over a network. A storage drive wirelessly communicates with other storage drives of the chassis, as well as one or more radio adapters of the chassis. The wireless controller corresponding to a storage drive is operative to wirelessly communicate with other wireless controllers corresponding to other storage drives and also with one or more radio adapters via wireless waveguides of the chassis. The one or more radio adapters are operative to communicate with other network devices external to the chassis and serve as access points to the chassis. Because the storage drives, the corresponding controllers, and the radio adapters communicate via wireless signals transmitted along waveguides, the chassis is a wireless chassis.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This Utility Patent Application is a Continuation of U.S. patentapplication Ser. No. 14/709,043 filed on May 11, 2015, now U.S. Pat. No.9,361,046 issued on Jun. 7, 2016, the benefit of which is claimed under35 U.S.C. §120, and which is further incorporated by reference in itsentirety.

TECHNICAL FIELD

The present invention relates generally to a multi-storage-drive datachassis that houses a plurality of non-specific storage drives, but moreparticularly, but not exclusively, to a wireless data storage chassisthat includes radio adapters and wave guides so that together withnetwork-addressable-storage-drive wireless controllers, the storagedrives are communicatively coupled to other network devices.

BACKGROUND

The use of distributed storage systems has grown in abundance over thepast few years. These systems often use a chassis that house multiplestorage drives, where data can be distributed across the various storagedrives. Typically, a single built-in chassis computer or stand-alonecomputer is used as an interface between the chassis (and accordinglyeach storage drive) and other network computers. This master computergenerally coordinates read and write operations, and sometimes datarecovery operations. However, if this master computer fails, then accessto the storage drives may be drastically reduced, slowed, or evenblocked to all of the drives of the chassis. Thus, it is with respect tothese considerations and others that the invention has been made.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the present invention, reference will bemade to the following Detailed Description, which is to be read inassociation with the accompanying drawings, wherein:

FIG. 1 is a system diagram of an environment in which embodiments of theinvention may be implemented;

FIG. 2 shows an embodiment of a network computer that may be included ina system such as that shown in FIG. 1;

FIG. 3A show embodiment of a wireless controller that may be includingin a system such as that shown in FIG. 1;

FIG. 3B shows an embodiment of a radio adapter;

FIG. 4 illustrates an exploded perspective view of a multi-storage-drivewireless chassis, a storage-drive carrier, a storage drive, a radioadapter, a waveguide, and a wireless controller in accordance withembodiments described herein;

FIG. 5 illustrates an exploded perspective view of another embodiment ofa wireless chassis that includes a waveguide bisected by a terminationplate and two radio adapters electromagnetically isolated from oneanother by the termination plate, in accordance with embodimentsdescribed herein;

FIG. 6 shows a schematic view of a wireless communication system thatincludes a plurality of storage drives, corresponding wirelesscontrollers, and a radio adapter electromagnetically coupled via awaveguide;

FIG. 7 shows a front schematic view of one embodiment of a tiledconfiguration of a plurality of non-specific storage drives andcorresponding wireless controllers electromagnetically coupled to avertical waveguide;

FIG. 8A shows top, front, and side views of an exemplary, butnon-limiting embodiment of a wireless data storage chassis shelfpopulated with a plurality of storage drives (“SD”) and correspondingwireless controllers (“WC”);

FIG. 8B shows a schematic view of a wireless chassis where a pluralityof waveguides communicatively couple corresponding storage drivecontrollers across a plurality of vertically stacked chassis shelves;

FIG. 9A shows a schematic view of an embodiment of a radio adapter thatis operative to electromagnetically couple to a plurality of waveguidesincluded in a wireless chassis;

FIG. 9B shows a schematic view of the plurality of channel elementsincluded in a radio adapter;

FIG. 10A shows a front view of an embodiment of a wireless data storagechassis that is consistent with the various embodiments disclosedherein;

FIG. 10B shows a front view of an embodiment of a redundant wirelessdata storage chassis that is consistent with the various embodimentsdisclosed herein;

FIG. 10C shows a front view of an embodiment of a geometricallymultiplexed wireless data storage chassis that is consistent with thevarious embodiments disclosed herein;

FIG. 10D shows a front view of an embodiment of a geometricallymultiplexed and redundant wireless data storage chassis that isconsistent with the various embodiments disclosed herein;

FIG. 11 illustrates a logical flow diagram generally showing anembodiment of a process for multiplexing or increasing a bandwidth of awireless data storage chassis;

FIG. 12A illustrates a logical flow diagram generally showing anembodiment of a process for multiplexing a frequency space within avolume of a chassis when wirelessly transmitting data;

FIG. 12B illustrates a logical flow diagram generally showing anembodiment of a process for multiplexing a frequency within a volume ofa chassis when wirelessly receiving data;

FIG. 13 illustrates employing multiple wireless signal paths tomultiplex an airspace within the volume of a chassis;

FIG. 14 illustrates a logical flow diagram generally showing anembodiment of a process for multiplexing an airspace within a volume ofa chassis by employing a multipath propagation of wireless signalswithin a waveguide;

FIG. 15A illustrates corrugations along the internal surfaces of awaveguide which are configured and arranged to provide multipletransmission paths for wireless signals within the waveguide; and

FIG. 15B illustrates structures disposed within an airspace of awaveguide which are configured and arranged to provide multipletransmission paths for wireless signals within the waveguide.

DETAILED DESCRIPTION OF THE INVENTION

Various embodiments are described more fully hereinafter with referenceto the accompanying drawings, which form a part hereof, and which show,by way of illustration, specific embodiments by which the invention maybe practiced. The embodiments may, however, be embodied in manydifferent forms and should not be construed as limited to theembodiments set forth herein; rather, these embodiments are provided sothat this disclosure will be thorough and complete, and will fullyconvey the scope of the embodiments to those skilled in the art. Amongother things, the various embodiments may be methods, systems, media, ordevices. Accordingly, the various embodiments may be entirely hardwareembodiments, entirely software embodiments, or embodiments combiningsoftware and hardware aspects. The following detailed descriptionshould, therefore, not be limiting.

Throughout the specification and claims, the following terms take themeanings explicitly associated herein, unless the context clearlydictates otherwise. The term “herein” refers to the specification,claims, and drawings associated with the current application. The phrase“in one embodiment” as used herein does not necessarily refer to thesame embodiment, though it may. Furthermore, the phrase “in anotherembodiment” as used herein does not necessarily refer to a differentembodiment, although it may. Thus, as described below, variousembodiments of the invention may be readily combined, without departingfrom the scope or spirit of the invention.

In addition, as used herein, the term “or” is an inclusive “or”operator, and is equivalent to the term “and/or,” unless the contextclearly dictates otherwise. The term “based on” is not exclusive andallows for being based on additional factors not described, unless thecontext clearly dictates otherwise. In addition, throughout thespecification, the meaning of “a,” “an,” and “the” include pluralreferences. The meaning of “in” includes “in” and “on.”

As used herein, the term “multi-storage-drive chassis” refers to astorage architecture that includes a chassis, backplane, and variousother circuitry (e.g., power supply, a centralized chassis controller,or the like) for enabling use of a plurality of storage drives. In someembodiments, a multi-storage-drive chassis may be in a non-RAID(non-Redundant Array of Independent Disks) architecture, such as, forexample, a JBOD (or “just a bunch of disks”) architecture. However,embodiments are not so limited, and in other embodiments, themulti-storage-drive chassis may be in a RAID architecture.

In various embodiments, the backplane of the chassis may include aplurality of connectors that are electrically coupled to the backplane.Some aspects of the connectivity may be in parallel; power for instance.Other connector connectivity can be star connected high speed serial.These connectors may be referred to as backplane connectors. In someembodiments, each backplane connector may be referred to as astorage-drive slot (or disk slot). The backplane connectors may enable aplurality of storage drives to electrically couple with the backplane.In at least one embodiment, the plurality of storage drives may receivepower through the backplane connectors.

In various embodiments, multi-storage-drive chassis may utilizestorage-drive carriers or trays to enable easy insertion and removal ofthe storage drives to and from the chassis. The storage-drive carrierscan provide easy and consistent alignment of a storage-drive's outputconnector and a backplane input connector.

In various embodiments, the multi-storage-drive chassis may use wirelesscommunication to connect a plurality of storage drives to an externalnetwork. The wireless multi-storage-drive chassis embodiments mayinclude one or more waveguides to facilitate secure and effectivewireless communication with the storage drives. The one or morewaveguides may be located in the chassis so that they extend from one,some, or all of the shelves of storage drives in the chassis. Inpreferred embodiments, at least one of the waveguides is configured andarranged to transmit wireless signals along a substantially verticalaxis of transmission. For instance, the wave guides may be substantiallyvertical waveguides extending between the shelves of the chassis. Invarious embodiments, one or more channels, or cavities, in thewaveguides are provided. Each channel may be formed in a waveguidehaving a shape that facilitates the communication of wireless signalsalong its length, such as a substantially circular, oval, rectangular,square, triangular, or the like shape.

In various embodiments, antennas corresponding to one or more radioadapters and one or more antennas corresponding to one or more wirelesscontrollers for the storage drives are able to wirelessly receive andtransmit wireless communication signals with each other within thewaveguide. The one or more radio adapters are also configured tofacilitate communication between one, some or all of the wirelesscontrollers and at least one network and/or network device that isremote to the chassis.

In various embodiments of the wireless multi-storage-drive chassis,multiple radio adapters may be located in one or more waveguides to atleast facilitate system redundancy and flexible bandwidth allocationwhen wirelessly communicating with one or more wireless controllers. Forexample, in various exemplary embodiments, two or more radio adaptersmay be arranged in one waveguide to provide redundant wirelesscommunication with each wireless controller in the multi-storage-drivechassis. Also, in other exemplary embodiments, multiple radio adaptersmay be separately located in different waveguides or isolated portionsof a waveguide to provide greater wireless communication flexibility andincreased communication bandwidth with different portions of theplurality of wireless storage drive controllers in the wirelessmulti-storage-drive chassis. For example, in various embodiments, oneportion of a plurality of wave guides may be arranged to enable wirelesscommunication between one portion of a plurality of wirelesscontrollers. And another different portion of the plurality of waveguides may be arranged to enable wireless communication between anotherdifferent portion of the plurality of radio adapters and anotherdifferent portion of the plurality of wireless controllers located inthe wireless multi-storage-drive chassis. Also, in various embodiments,the one or more radio adapters may be located along the length of one ormore of the waveguides and/or at one or both ends of each waveguide.

Additionally, in various embodiments, one or more termination plates forwireless signals within a wave guide may be arranged at one or both endsof a waveguide to prevent reflections and standing waves of wirelesscommunication signals within the waveguide. In at least one embodiment,a termination plate is positioned to partition or subdivided one or morewaveguides into multiple, electromagnetically isolated waveguideportions. Also, the interior surface of one or more channels in awaveguide may be irregular to support MIMO spatial multiplexingoperation based on multipath inducing geometry within the waveguide'schannel. For example, the waveguide's interior surface may includesymmetrical and/or non-symmetrical ridges, angles, shapes, folds,corrugations, or protuberances that are placed at symmetrical and/ornon-symmetrical locations along the interior surface of the waveguide'schannel. Furthermore, in at least one embodiment, one or more obstaclesare positioned within the transmitting cavity of a waveguide to enablespatial multiplexing.

In various embodiments, the wireless multi-storage-drive chassis is notlimited for use with waveguides to provide wireless communication.Instead, the chassis may be provided without waveguides and employ oneor more radio adapters that can wirelessly communicate with one or morewireless controllers separate from a waveguide. Further, in variousembodiments, the chassis may be provided with waveguides for a portionof storage drives having wireless controllers, and wired connections forother storage drives having controllers with a second connector.

In various embodiments, the types of wireless communication protocolsemployed by the radio adapters and the wireless controllers may be astandard protocol or one of its variants, for example, WiFi (IEEE802.11), Bluetooth (IEEE 802.15.1), WiMax (IEEE 802.16), WiMax MIMO,WiMax MISO, ZigBee (IEEE 802.15.4), MiWi (IEEE 802.15.4), or the like.The wireless communication signals may also be communicated with amodified standard wireless protocol, and/or a proprietary wirelessprotocol.

In some embodiments, a chassis includes one or more remote communicationinterfaces. The communication interfaces are operative to providecommunication with at least one network and/or network device that isremote to the chassis. The remote communication interfaces may be incommunication with the radio adapters. For instance, a remotecommunication interface of the chassis may be operative to communicate(via wire or wirelessly) with an external communication interface of aradio adapter. In at least one embodiment, at least one remotecommunication interface is included in a radio adapter. A remotecommunication interface of the chassis may be integrated with a externalcommunication interface of a radio adapter.

As used herein, the term “radio adapter” refers to an electroniccomponent, device, computer, and the like, that is located in a wirelessmulti-storage-drive chassis and provides wireless communication with oneor more wireless storage drive controllers. Also, in variousembodiments, the radio adapter enables communication between thechassis' storage devices (i.e., each wireless controller) and at leastone network and/or network device that is remote to the chassis. Anexternal communication interface of the radio adapter may at leastpartially enable communication with the network device. As discussedabove, an external communication interface of a radio adapter may be incommunication with, or integrated with, a remote communication interfaceof the chassis to provide communication over a network with remotelylocated network computers.

Also, in various embodiments, the communication with the at least onenetwork and/or remote network device may be based on Ethernet, or thelike. Additionally, in various embodiments, the radio adapter may employa fiber optic connection, or some other high bandwidth connection, tocommunicate with the at least one network and/or remote network device,or the like. In at least one embodiment, the communication between theradio adapter and the at least one network and/or remote network devicemay be a wireless communication.

In various embodiments, the radio adapter may include one or moreantennas that enable wireless communication with one or more wirelesscontrollers and/or one or more radio adapters that are at least locatedin the wireless multi-storage-drive chassis. In various embodiments, theradio adapter may be configured to wirelessly communicate through achannel or cavity in a waveguide with one or more wireless controllersand/or one or more other radio adapters. In various embodiments, theradio adapter may include one or more antennas for enabling wirelesscommunication with one or more wireless controllers and/or one or moreother radio adapters that communicate outside of a waveguide.

As used herein, the term “storage drive” refers to a device for storingdata. The various embodiments described herein can utilize most typical,non-specific, or general storage drive on the market (i.e., the storagedrive itself does not need to include or be modified to include anycircuitry, components, or the like to perform the various embodiments).Storage drives may include hard disk drives (HDD), solid state drives(SSD), optical drives, or the like.

In various embodiments, storage drives may include a housing that hastwo ends, a top, a bottom, and two sides. In various embodiments, a backend of the storage-drive housing may include a storage-drive connector.In at least one of various embodiments, the back end of the housing mayinclude peripheral edges (e.g., the perimeter edges of the back end ofthe storage-drive housing).

Storage drives can come in many different form factors, such as, forexample, 3.5 inch, 2.5 inch, 1.8 inch, 5.25 inch, 8 inch, or the like.It should be understood that the actual dimensions of the storage drive(including the housing and/or storage-drive connector) may be differentthan the form factor nomenclature based on industry standards. Somemulti-storage-drive chassis may support only one form factor, whileother multi-storage-drive chassis may support multiple form factors(e.g., backplane connectors may be compatible with storage drives havingdifferent factors and the storage-drive carriers may be adaptable fordifferent form factors). Although the specification is primarilydescribed in terms of storage drives having a 3.5 inch form factor,embodiments are not so limited. But, rather, other types of storagedrives, form factors, and/or chassis may be employed.

Along with different form factors, storage drives can include differentconnectors for connecting to a multi-storage-drive-chassis backplane.These connectors may be referred to as storage-drive connectors and maybe compatible with the backplane connectors. A storage-drive connectormay be a SAS connector, SATA connector, universal serial bus (USB),firewire (or IEEE 1394), thunderbolt, PATA (Parallel Advanced TechnologyAttachment) connector, SCSI connector, Fibre Channel (FC) connector,Enhanced Integrated Drive Electronics (EIDE) connector, or the like.

Storage drives may have different power consumption profiles dependingon various states of the storage drive, type of storage drive, or thelike. Some of the different states of a storage drive may be an initialstart-up power state; an idle state, an initial access state, and asustained read//write state. The initial start-up power state may bewhen an initial amount of power is provided to the storage drive for thestorage drive to provide basic communication with other devices. Theidle state may be while the storage drive is awaiting a read/writerequest. The initial access state may be an initial amount of powerrequired to make a read or write of the drive (e.g., an initial powerrequired to start spinning the disk of a HDD). The sustained read/writestate may be while a storage drive is fulfilling a read or write requestafter the initial read/write state.

As used herein, the term “controller” or “controller computer” refers toa computer or physical device that is separate from atypical/non-specific/general storage drive and separate from amulti-storage-drive chassis, but can be electrically coupled between anindividual storage drive and the chassis backplane.

Briefly, the controller can accept data in a storage drive supportedprotocol through a storage-drive connector and wirelessly provide thedata to other controllers or to a radio adapter. Accordingly, suchcontrollers are wireless controllers. The controllers convert theaccepted data into a supported protocol, such as any wireless protocolfor output through a wireless interface. The wireless interface isenabled to transmit the data, via a waveguide included in a wirelessdata storage chassis. Similarly, the controller can accept data in thewireless protocol through the waveguide and convert it to a storagedrive supported protocol for output through the storage-drive connectorto the storage drive. In various embodiments, each controllereffectively makes each separate storage drive individually networkaccessible by other controllers and/or network computers.

In various embodiments, the wireless controller may include one or morewireless interfaces with antennas that enable communication with one ormore radio adapters and/or one or more other wireless controllerslocated in a wireless multi-storage-drive chassis. The wirelessinterfaces may be removed and exchanged and/or reprogrammed toaccommodate at least a wireless communication protocol employed by acorresponding radio adapter. The wireless controller may be configuredto wirelessly communicate through a channel in a waveguide, and/oroutside of a waveguide, with one or more other wireless controllersand/or one or more other radio adapters. The wireless controller mayinclude one or more antennas for wirelessly communicating. Also, thewireless controller may include a connector for receiving power from awireless multi-storage-drive chassis. In various embodiments, thewireless controller enables communication between the chassis' storagedevices and one or more radio adapters over a high bandwidth wirelessconnection, e.g., a WiFi 802.11ad. In at least one embodiment, thewireless interfaces receive and transmit data outside of a waveguide.

In various embodiments, the controller may have a first connector, awireless interface, a processor, memory, and other peripheral circuitry.In various embodiments, the processor and memory (and other peripheralcircuitry) may be mounted on a circuit board, such as a printed circuitboard (PCB). The first connector is positioned on the side of the PCBthat faces a storage drive. The processor, memory, and peripherycircuitry may be mounted on either side of the PCB.

The first connector may be a connector that can couple with astorage-drive connector. The wireless interface electromagneticallycouples the controller to the waveguide. The first connector may beselected based on the storage-drive connector, so that the firstconnector and the storage-drive connector are compatible (e.g., thestorage-drive connector may be a male connector, which can mate with afemale first connector on the controller). In at least one of variousembodiments, the first connector may be a SATA connector (but otherconnectors may be employed). In various embodiments, the types ofconnectors that may be utilized for the first connector may include, forexample, SAS connector, SATA connector, universal serial bus (USB),firewire (or IEEE 1394), thunderbolt, PATA (Parallel Advanced TechnologyAttachment) connector, SCSI connector, Fibre Channel (FC) connector,Enhanced Integrated Drive Electronics (EIDE) connector, or the like.

In some embodiments, the controller board may be a universal board thatcan accept different types of first connectors and/or wirelessinterfaces. In at least one of various embodiments, a user may beenabled to affix the first connector and/or the wireless interface tothe controller board. For example, assume a user has amulti-storage-drive chassis that includes one or more waveguides toelectromagnetically couple a plurality of wireless controllers and oneor more radio adapters. Further assume that the user has three storagedrives with SATA connectors and three storage drives with USBconnectors. In this example, the user can put together six differentcontrollers, three controllers with a SATA connector as first connectorand a wireless interface to transmit and receive wireless signals viathe waveguide, and three other controllers with a USB connector as thefirst connector and a wireless interface to transmit and receivewireless signals via the waveguide. This universal controller board canenable a user to use virtually any storage drive (with acontroller-supported connector type) with virtually any wirelessmulti-storage-drive chassis, regardless of the storage drive and chassishaving connectors that are compatible with each other.

In various embodiments, the controller may have dimensions that fit intothe form factor shadow of the storage drive. As described in more detailherein, a circuit board of the controller may have a shape that fitswithin the dimensions of a lateral cross-section of the storage drive.Similarly, the overall size of the controller may be determined suchthat the controller and storage drive—when coupled together—iscompatible with a drive carrier for the multi-storage-drive chassis. Invarious embodiments, “fitting into the form factor shadow of the storagedrive” may refer to a physical shape of the controller being operativeto fit adjacent to a correspondingly coupled storage drive connector andoccupy less space than is bounded by peripheral edges of an end of aseparate housing of a storage drive coupled to the storage driveconnector. In some embodiments, this physical shape of the controllermay fit into the peripheral edges of a lateral-cross second of thestorage drive.

As described in more detail herein, a wireless controller may beoperative to control/manage a single storage drive. So, unlike a mastercomputer that would control/manage a plurality of storage drives, eachcontroller individually controls/manages its own correspondingindividual storage drive. Although, in various embodiments, controllersmay wirelessly communicate with each other to coordinate and performtasks between a plurality of storage drives. In some embodiments,controllers can wirelessly communicate locally (without accessing thechassis interface for communication with external/remote devices) withother controllers through the one or more waveguides included in thewireless chassis via wireless protocols.

In various embodiments, a controller can individually determine one ormore power-up sequences and/or manage the voltage and/or power suppliedto its corresponding storage drive (i.e., the storage drive that thecontroller is coupled to). In other embodiments, a plurality ofcontrollers can coordinate with each other to schedule power-upsequences for a plurality of storage drives (e.g., to minimize the powerspike effects of powering up multiple storage drives at the same time).

In other embodiments, the controller may monitor various performancecharacteristics of its corresponding drive (e.g., power consumption,temperature, response time/latency, or the like) to providecomprehensive storage drive analytics and diagnostics at the individualdrive level. This type of monitoring can allow a controller to identifythat its corresponding drive may be about to fail (e.g., changes inpower consumption, temperatures above a threshold, increased latency, orthe like), and coordinate with other controllers (or an administrator)to backup the potentially failing drive's data, halt future writeoperations to potentially failing drive, or the like.

It should be noted that these examples of wireless controllerfunctionality are for illustration purposes and should not be construedas limiting, and that each controller may perform additional tasksand/or actions at the individual storage drive level and/or coordinatewith each other to perform tasks and/or actions across a plurality ofstorage drives.

As used herein, the term “waveguide” refers to any structure that isconfigured and arranged to guide or otherwise enable the transmission orpropagation of an electromagnetic (“EM”) wave. The direction of thewave's transmission or propagation is substantially defined bycharacteristics of the waveguide. In various embodiments, a waveguide isconfigured and arranged to transmit wireless communication signalsbetween one or more wireless interfaces of a plurality of wirelesscontrollers housed within a chassis. Furthermore, a waveguide may beconfigured and arranged to transmit wireless communication signalsbetween one or more wireless interfaces of a wireless controller and awireless interface of a radio adapter, where at least one of thewireless controller or the radio adapter is housed within a wirelesschassis. Thus, a waveguide may be a wireless waveguide.

In various embodiments, a waveguide includes a cavity, and the wirelesssignals are transmitted along an airspace within the cavity. Theinternal walls or surfaces of the cavity may be electrically conductive.In at least one embodiment, a waveguide is a conducting pipe or pipesegment. The lateral cross-sectional shape of the pipe may be of anyshape, including but not limited to oval, circular, square, rectangular,triangular, or any other such shape.

As described herein, a waveguide's interior surfaces may includesymmetrical and/or non-symmetrical ridges, angles, shapes, folds,corrugations, or protuberances that are placed at symmetrical and/ornon-symmetrical locations along the interior surface of the waveguide'schannel. Such structures on the interior surfaces of a waveguide areoperative to create multiple signal paths or noise in signalstransmitted along the airspace in the cavity. Such multiple signal pathsare employed to support MIMO or MIMO-like multiplexing of the airspacewithin the cavity. Structures, such as obstacles, wave splitters,reflectors, or the like may be positioned within the cavity to providethe multiple signal paths. Such obstacles may include conductivesurfaces that are configured and arranged to reflect incident EM waves.

Characteristics of the waveguide, including a cross-sectional shapeand/or lateral dimensions may be based on various characteristics of theEM waves to be transmitted. For instance, a lateral cross-sectionalshape and/or a lateral dimension of the waveguide may be based on therange of frequencies or wavelengths of the signals to be transmitted. Inpreferred embodiments, one or more characteristics of a waveguide arebased on enabling the transmission and guidance of a wireless signalconsistent with a wireless protocol or standard, such as, but notlimited to WiFi (IEEE 802.11), Bluetooth (IEEE 802.15.1), WiMax (IEEE802.16), WiMax MIMO, WiMax MISO, ZigBee (IEEE 802.15.4), MiWi (IEEE802.15.4), or the like. In at least one embodiment, a waveguide is aRadio Frequency (“RF”) waveguide because the waveguide is operative totransmit EM waves within the RF portion of the EM spectrum.

Waveguides may confine the EM waves to within the waveguide. In apreferred embodiment, a waveguide enables total or near-total internalreflection (from the internal conductive walls of the cavity) of thewaves within the waveguide. As the EM wave propagates along thedirection of waveguide, the transmission is not substantiallyattenuated. Thus, the power loss of a signal within the waveguide isminimal. Furthermore, the signal is not substantially detectable outsideof the waveguide, i.e. the waveguide is not a “leaky” waveguide.Accordingly, a signal within the waveguide is detectable within thecavity, but is not practically detectable outside the cavity. A device,such as a wireless interface of a network device, is said to be“electromagnetically coupled” to a waveguide if the device is operativeto receive, transmits, or otherwise detect a wireless signal within thewaveguide.

The following briefly describes embodiments of the invention in order toprovide a basic understanding of some aspects of the invention. Thisbrief description is not intended as an extensive overview. It is notintended to identify key or critical elements, or to delineate orotherwise narrow the scope. Its purpose is merely to present someconcepts in a simplified form as a prelude to the more detaileddescription that is presented later.

Briefly stated, various embodiments are directed to a data storagechassis for storing a plurality of non-specific storage drives,corresponding wireless controllers, and one or more radio adapters. Atleast a portion of the storage drives are operative to communicate withanother portion of the storage drives and with another network deviceover a network. A storage drive of the chassis wirelessly communicateswith other storage drives of the chassis, as well as one or more radioadapters of the chassis. The wireless controller corresponding to aspecific storage drive is operative to wirelessly communicate with otherwireless controllers corresponding to other storage drives and also oneor more radio adapters via waveguides of the chassis. The one or moreradio adapters are operative to communicate with other network devicesexternal to the chassis. Accordingly, the one or more radio adapters mayserve as access points or wireless switches to the chassis. Because thestorage drives, the corresponding controllers, and the radio adapterscommunicate via wireless signals, the chassis is a wireless chassis.

In various embodiments, a wireless chassis does not include, or at leastincludes less of: wires, Ethernet switches, switching fabrics, becausethe communication between the storage drives and external networkdevices is at least partially enabled by wireless: waveguides,controllers, and radio adapters. Accordingly, the storage density of awireless chassis is increased. Additionally, the cost of a wirelesschassis is reduced due to the reduced wiring costs and the readyavailability of wireless communication hardware. Also due to the reducedwiring and hardware requirements, a wireless chassis is simpler andeasier to install and maintain.

A wireless chassis may include an increased bandwidth. Furthermore, thebandwidth may be dynamically allocated during the operation of thewireless chassis based on real time or near-real time operatingconditions or requirements. In various embodiments, the bandwidth of awireless chassis is increased by multiplexing at least one of: afrequency space within the chassis, an airspace within the chassis, or ageometry of the chassis. For instance, a frequency space may bemultiplexed by at least transmitting multiple wireless signals within asingle waveguide, wherein frequency channels of the multiple signals aredistributed among a frequency band. Thus, a single waveguide may bemultiplexed into a plurality of frequency channels.

An airspace within the chassis may be multiplexed by providing employingmultiple transmitting and multiple receiving antennas to employ themultipath wave propagation within a single waveguide, such as a MIMO orMIMO-like spatial multiplexing. In at least one embodiments, individualchannels within a single waveguide are defined by walls are otherstructures internal to the waveguides. Additionally, the geometry of thechassis may be multiplexed by providing separate and distinct waveguideswithin the chassis. In some embodiments, a single waveguide ismultiplexed into two separate waveguide portions by a termination plate,or other such structure. Such multiplexing may be dynamically adjustedto meet the real time or expected bandwidth needs of the chassis.

More specifically, various embodiments are directed to an apparatus orsystem, such as a wireless data storage chassis, for storing a pluralityof non-specific storage drives. The plurality of storage drives areoperative to communicate over a network. Furthermore, a bandwidth forwireless communication between the plurality of storage drives andanother network device separate from the chassis is increased bymultiplexing at least one of: a frequency space, an airspace, or ageometry of a chassis or apparatus.

Various embodiments of the apparatus include a housing. The housinghouses or otherwise contains the plurality of storage drives, one ormore radio adapters, one or more wireless waveguides, and one or moreremote communication interfaces. Each of the storage drives includes oneor more wireless controllers. The radio adapters include wirelessinterfaces and communication interfaces. The radio adapters perform atleast one of: multiplexing frequencies of wireless signals communicatedin an airspace between the one or more radio adapters and the one ormore wireless controllers or multiplexing wireless signals communicatedbetween the one or more radio adapters and the one or more wirelesscontrollers based on one or more characteristics of the airspace.

The wireless waveguides include an internal cavity for the airspace. Theinternal cavity may guide the transmission of the wireless signalsbetween the wireless controllers and the wireless interfaces of theradio adapters. The remote communication interfaces providecommunication over the network with one or more remotely located networkcomputers. The remote communication interfaces are in communication withthe external communication interfaces of the radio adapters.

Illustrative Operating Environment

FIG. 1 shows components of one embodiment of an environment in whichvarious embodiments of the invention may be practiced. Not all of thecomponents may be required to practice the various embodiments, andvariations in the arrangement and type of the components may be madewithout departing from the spirit or scope of the invention. As shown,system 100 of FIG. 1 may include wireless multi-storage-drive chassis110, network computers 102-105, and network 108.

Network computers 102-105 may communicate with multi-storage-drivechassis 110 via network 108. Network 108 may be configured to couplenetwork computers with other computing devices, including networkcomputers 102-105, multi-storage-drive chassis 110, other networks, orthe like. In various embodiments, information communicated betweendevices may include various kinds of information, including, but notlimited to, processor-readable instructions, client requests, serverresponses, program modules, applications, raw data, control data, videodata, voice data, image data, text data, or the like. In someembodiments, this information may be communicated between devices usingone or more technologies and/or network protocols.

In some embodiments, network 108 may include various wired networks,wireless networks, or any combination thereof. In various embodiments,network 108 may be enabled to employ various forms of communicationtechnology, topology, computer—readable media, or the like, forcommunicating information from one electronic device to another. Forexample, network 108 can include—in addition to the Internet—LANs, WANs,Personal Area Networks (PANs), Campus Area Networks (CANs), MetropolitanArea Networks (MANs), direct communication connections (such as througha USB port), or the like, or any combination thereof.

In various embodiments, communication links within and/or betweennetworks may include, but are not limited to, twisted wire pair, opticalfibers, open air lasers, coaxial cable, plain old telephone service(POTS), wave guides, acoustics, full or fractional dedicated digitallines (such as T1, T2, T3, or T4), E-carriers, Integrated ServicesDigital Networks (ISDNs), Digital Subscriber Lines (DSLs), wirelesslinks (including satellite links), or other links and/or carriermechanisms known to those skilled in the art. Moreover, communicationlinks may further employ any of a variety of digital signalingtechnologies, including without limit, for example, DS-0, DS-1, DS-2,DS-3, DS-4, OC-3, OC-12, OC-48, or the like. In some embodiments, arouter (or other intermediate network device) may act as a link betweenvarious networks—including those based on different architectures and/orprotocols—to enable information to be transferred from one network toanother. In other embodiments, network computers and/or other relatedelectronic devices could be connected to a network via a modem andtemporary telephone link. In essence, the network may include anycommunication technology by which information may travel betweencomputing devices.

Network 108 may, in some embodiments, include various wireless networks,which may be configured to couple various portable network devices,remote computers, wired networks, other wireless networks, or the like.Wireless networks may include any of a variety of sub-networks that mayfurther overlay stand-alone ad-hoc networks, or the like, to provide aninfrastructure-oriented connection for at least network computers103-105. Such sub-networks may include mesh networks, Wireless LAN(WLAN) networks, cellular networks, or the like. In at least one of thevarious embodiments, the system may include more than one wirelessnetwork.

Network 108 may employ a plurality of wired and/or wirelesscommunication protocols and/or technologies. Examples of variousgenerations (e.g., third (3G), fourth (4G), or fifth (5G)) ofcommunication protocols and/or technologies that may be employed by thenetwork may include, but are not limited to, Global System for Mobilecommunication (GSM), General Packet Radio Services (GPRS), Enhanced DataGSM Environment (EDGE), Code Division Multiple Access (CDMA), WidebandCode Division Multiple Access (W-CDMA), Code Division Multiple Access2000 (CDMA2000), High Speed Downlink Packet Access (HSDPA), Long TermEvolution (LTE), Universal Mobile Telecommunications System (UMTS),Evolution-Data Optimized (Ev-DO), Worldwide Interoperability forMicrowave Access (WiMax), time division multiple access (TDMA),Orthogonal frequency-division multiplexing (OFDM), ultra wide band(UWB), Wireless Application Protocol (WAP), user datagram protocol(UDP), transmission control protocol/Internet protocol (TCP/IP), anyportion of the Open Systems Interconnection (OSI) model protocols,session initiated protocol/real-time transport protocol (SIP/RTP), shortmessage service (SMS), multimedia messaging service (MMS), or any of avariety of other communication protocols and/or technologies. Inessence, the network may include communication technologies by whichinformation may travel between network computers 102-105,multi-storage-drive 110, other computing devices not illustrated, othernetworks, or the like.

In various embodiments, at least a portion of the network may bearranged as an autonomous system of nodes, links, paths, terminals,gateways, routers, switches, firewalls, load balancers, forwarders,repeaters, optical-electrical converters, or the like, which may beconnected by various communication links. These autonomous systems maybe configured to self-organize based on current operating conditionsand/or rule-based policies, such that the network topology of thenetwork may be modified.

At least one embodiment of network computers 102-105 is described inmore detail below in conjunction with network computer 200 of FIG. 2.Briefly, in some embodiments, network computers 102-105 may beconfigured to communicate with multi-storage-drive chassis 110 to enabledistributed storage. In some embodiments, network computers 102-105 maycommunicate with individual controllers (e.g., controllers 114) for eachstorage drive associated with multi-storage-drive chassis 110 (e.g.,storage drives 116) to perform reads and writes of data, accessinformation and/or analytics, or the like. In various embodiments,network computers 102-105 may be remote and/or separate from chassis 110and controllers 114.

In some embodiments, at least some of network computers 102-105 mayoperate over a wired and/or wireless network (e.g., network 108) tocommunicate with other computing devices and/or multi-storage-drivechassis 110. Generally, network computers 102-105 may include computingdevices capable of communicating over a network to send and/or receiveinformation, perform various online and/or offline activities, or thelike. It should be recognized that embodiments described herein are notconstrained by the number or type of network computers employed, andmore or fewer network computers—and/or types of network computers—thanwhat is illustrated in FIG. 1 may be employed.

Devices that may operate as network computers 102-105 may includevarious computing devices that typically connect to a network or othercomputing device using a wired and/or wireless communications medium.Network computers may include portable and/or non-portable computers. Insome embodiments, network computers may include client computers, servercomputers, or the like. Examples of network computers 102-105 mayinclude, but are not limited to, desktop computers (e.g., networkcomputer 102), personal computers, multiprocessor systems,microprocessor-based or programmable electronic devices, network PCs,laptop computers (e.g., network computer 103), smart phones (e.g.,network computer 104), tablet computers (e.g., network computer 105),cellular telephones, display pagers, radio frequency (RF) devices,infrared (IR) devices, Personal Digital Assistants (PDAs), handheldcomputers, wearable computing devices, entertainment/home media systems(e.g., televisions, gaming consoles, audio equipment, or the like),household devices (e.g., thermostats, refrigerators, home securitysystems, or the like), multimedia navigation systems, automotivecommunications and entertainment systems, integrated devices combiningfunctionality of one or more of the preceding devices, or the like. Assuch, network computers 102-105 may include computers with a wide rangeof capabilities and features. In some embodiments, network computers102-105 may be referred to as remote computers, because they accessand/or store data on a different computer/device, such asmulti-storage-drive chassis 110. In some embodiments,multi-storage-drive chassis 110 may be maintained at a location that isseparate from network devices 102-105 (e.g., cloud computing/storagethat utilize distributed storage systems).

Network computers 102-105 may access and/or employ various computingapplications to enable users of network computers to perform variousonline and/or offline activities. Such activities may include, but arenot limited to, generating documents, gathering/monitoring data,capturing/manipulating images, managing media, managing financialinformation, playing games, managing personal information, browsing theInternet, or the like. In some embodiments, network computers 102-105may be enabled to connect to a network through a browser, or otherweb-based application.

Network computers 102-105 may further be configured to provideinformation that identifies the network computer. Such identifyinginformation may include, but is not limited to, a type, capability,configuration, name, or the like, of the network computer. In at leastone embodiment, a network computer may uniquely identify itself throughany of a variety of mechanisms, such as an Internet Protocol (IP)address, phone number, Mobile Identification Number (MIN), media accesscontrol (MAC) address, electronic serial number (ESN), or other deviceidentifier.

Multi-storage-drive chassis 110 may include backplane 112 and may beconfigured to house a plurality of separate storage drives, such asstorage drives 116, which may include more or less devices than what isillustrated in the figure. In some embodiments, each storage drive mayutilize (e.g., be fastened to) a storage carrier or tray (not shown) forinsertion into the chassis. However, in some embodiments, the storagedrives may be affixed directly to the chassis. As described herein, aseparate controller (e.g., wireless controllers 114) may be coupled toeach separate storage drive and the combination of the storage drive andcontroller may be coupled to backplane 112. Each of wireless controllers114 may provide a separately addressable network interface for each ofstorage drives 116.

In various embodiments, chassis 110 may be configured and/or modified toprovide aired and/or wireless communication access to backplane 112. Inat least one embodiment, backplane 112 may provide wirelesscommunication access to each of controllers 114 through one or morewaveguides that wirelessly couples the controllers 114 to a radioadapter. In some embodiments, chassis 110 may include an Ethernet portand/or interface component for connecting chassis 110 to network 108.

Wireless controllers 114 may directly communicate with network computers102-105. In various embodiments, each of controllers 114 may convertdata received from its corresponding storage drive 116 into an Ethernetprotocol and communicated to network computers 102-105 via backplane 112and network 108. Similarly, each controller may convert data receivedfrom network computers 102-105 (via network 108 and the Ethernetconnection supported by backplane 112) into a storage drive protocol foraccessing its own corresponding storage drive.

Since storage drives 116 can be of any typical/non-specific/generalstorage drive/agnostic, each of controllers 114 may perform differenttypes of data protocol conversions depending on the type storage drivethat it is coupled with. In this way, each storage drive can beindividually addressable and network computers 102-105 can individuallyaccess each separate storage drive 116 via an Ethernet protocol withouthaving to utilize a centralized/master controller—either a chassiscontroller or a standalone computer that centrally manages access toeach storage drive 116. So, in various embodiment, each separatecontroller (of controllers 114), and thus each separate storage drive,is individually addressable and can be individually accessed by networkdevices 102-105.

In various embodiments, controllers 114 may wirelessly communicate witheach other via a waveguide enabled connection of backplane 112 to employvarious storage drive management actions, monitoring actions, or thelike. So in some embodiments, controllers 114 may communicate with eachother—independent of a chassis controller or otherprimary/main/master/coordinator computer—to perform various actions(some of which may be done in parallel), including, but not limited to,data reads, data writes, data recovery, or the like.

For example, in some embodiments, the controllers may communicate witheach other to perform distributed data storage actions among a pluralityof storage drives. In one non-limiting example, network computer 102 mayprovide a write request to controller 118 (in some embodiments, thisrequest may go through a load balancer or other routing device).Controller 118 may work together with the separate controllers 114 tocoordinate the write request across one or more of storage drives 116(even if the network computer is unaware of the other controllers and/orstorage drives). In this example, controller 118 may coordinate with theother controllers of controllers 114 to determine whichcontroller/storage drives will store what data. Since each controller114 is network accessible (e.g., IP addressable), in some embodiments,network computer 102 may be able to individually access each storagedrive 116 and indicate which storage drives will store what data.

Similarly, the controllers may communicate with each other to recoverlost data. For example, assume there are 20 storage drives that arelogically separated into four clusters, and each drive is coupled to acontroller, as described herein. If one of the drives in a singlecluster fails and the other drives in the same cluster are configured toand able rebuild the lost data of the failed drive, then the controllersassociated with the drives in that cluster can coordinate the rebuild ofthe lost data, while the other 15 drives continue to perform data reads,writes, or the like.

In some other embodiments, controllers 114 may manage and coordinatepower utilization of storage drives 116. In various embodiments, powerconsumption management and/or power management of a storage drive mayinclude enabling and/or disabling various features of a storage drive.For example, a controller can manage the power consumption of itscorrespondingly coupled storage drive by providing different commands(e.g., through the command set) to the storage drive to enable/disablevarious features of the storage drive. In other embodiments, powermanagement may include switching the power rails (e/g/. +3.3V, +5V and+12V) on and off.

In various embodiments, controllers 114 may communicate with each otherto coordinate a schedule for powering up storage drives 116. In someembodiments, each controller 114 may be operative to determineparameters and/or capabilities of its corresponding storage drive. Thisdetermination may be based on a type of connector that is coupled to thestorage drive (i.e., the first connector), previously stored powerconsumption profile of the storage drive, drive identifier, or the like.

Based on the parameters and/or capabilities of each storage drive in thechassis, controllers 114 may determine an efficient way of powering upthe storage drives to reduce spikes in power consumption by the storagedrives (i.e., each controller may determine various power-up sequencesfor its correspondingly coupled storage drive). In particular,mechanical drives (e.g., HDDs) may have an initial spike in powerconsumption when they turn on due to the electrical properties ofpowering up the motor to drive the disk. This power consumption can becompared to that of SSDs, which typically is a more step function whenthe drive is powered up.

Since each controller can manage the power supplied to its correspondingstorage drive, and since there is no need for the drives to be of auniform type (or model, or from a same manufacturer), the controllers asa group can determine and employ a power-up schedule that can allow oneor more of the storage drives to power up before other storage drivesare powered up. For example, in some embodiments, each of the mechanicaldrives (e.g., HDD) may be power up before the SSDs on the same chassis.Similarly, each the power up of each drive may be slightly staggered tofurther reduce the issues that can arise from a spike in powerconsumption. By optimizing the schedule for powering storage drives 116.

Similarly, a controller can individually and dynamically adjust thepower of its corresponding drive at any given time. In this way, eachcontroller can individually or collectively monitor the temperature ofthe various drives and adjust their power individually.

This type of drive-specific power control can enable a controller toreduce a drive's power—e.g., if the drive has a temperature above athreshold in an attempt to give the drive time to cool down. In otherembodiments, a controller can increase or decrease the power supplied toits correspondingly coupled storage drive based on trade-offs betweenpower consumption, speed of accessing data, regularity or frequency ofaccess requests, or the like. In yet other embodiments, a plurality ofcontrollers can coordinate to reduce power consumption on a per drivebasis across a plurality of storage drives. So, in some embodiments, thecontroller may individually monitor and adjust the power supplied to anindividual storage drive or may work collectively to manage/adjust thepower supplied to the plurality of storage drives.

This type of control at the drive level can allow for reduced powerconsumption during various times of the day. For example, if somestorage drives are idle for a predetermined time and the current time isat a peak price for energy (e.g., dollars per kilowatt used), then thecontrollers for those storage drives may individually reduce the powersupplied to those storage drives—while other storage drives (that areaccessed more recently) are maintained at a higher power. Therefore, auser of the chassis can save money on energy costs without greatlyaffecting performance.

Since each separate storage drive is managed by a separate controller,each controller can provide individualized management and/or monitoringof a corresponding storage drive. For example, in some embodiments, acontroller can monitor power consumption, temperature, or otherperformance characteristics of the coupled storage drive and providethose monitored analytics to one of network computers 102-105 or toanother controller. In at least one such embodiment, if a controllerdetermines that its corresponding storage drive is operating at atemperature above a given threshold, the controller can reduce the powerconsumption of the drive or power it down completely (e.g., until thedrive temperature falls below another threshold value).

In other embodiments, the controller may identify that its correspondingdrive is exhibiting performance characteristics of a failing drive(e.g., extra power consumption, overheating, excessive latency (e.g.,above a time threshold) while performing a read/write operation, or thelike), then the controller can notify the other controllers (or one ormore of network devices 102-105) that its drive may be about to fail.Once notified of the possible failure, the controllers can take steps toanticipate the failure. Such anticipation may include employing othercontrollers to write to other non-failing drives, initiate copying ofthe failing drive to a spare drive (that also has a correspondingcontroller), or the like.

In various other embodiments, the combined/coupled storage drive andcontroller may utilize hot swap features of chassis 110.

In some embodiments, controllers 114 may cooperatively coordinate witheach other in a peer-to-peer architecture to control/manage operationsof each correspondingly coupled storage drive 116, as described herein.In other embodiments, controllers 114 may cooperatively coordinatestorage-drive-operation control/management with each other as more of aserver-to-peer architecture, where one of controllers 114 may operate asa master controller and one or more of the other controllers ofcontrollers 114 may operate as slave controllers.

In at least one such architecture, the slave controllers may provideinformation (e.g., storage-drive characteristics, performanceparameters, or the like) to the master controller. The master controllercan determine storage-drive power-up sequences and/or schedules,identify potentially failing storage drives, coordinate backup and/orrecovery of a potentially failing (or already failed) storage drive, orthe like, as described herein. Based on these determinations, the mastercontroller may provide instructions to one or more of the slavecontrollers for managing their correspondingly coupled storage drives.For example, the master controller may provide separate instructions toeach slave controller, which may separately indicate when and/or how aslave controller is to power-up its correspondingly coupled storagedrive (noting that the master controller may also have a correspondinglycoupled storage drive that may be managed/controlled in conjunctionswith the other storage drives). In other embodiments, the controllersmay communicate information amongst each other without directlyaccessing, managing, or otherwise controlling the storage drives.

In various other embodiments, a network computer (e.g., one of networkcomputers 102-105, which may be remote to chassis 110) and controllers114 may operate in a server-to-peer architecture to control/manageoperations of one or more storage drives 116 in chassis 110 (or storagedrives in multiple chassis)—similar to that which is described above. Inat least one such embodiment, the network computer may operate as amaster network computer and controllers 114 may operate as slavecontrollers. In various embodiments, the network computer (e.g., amaster network computer) may coordinate and/or instruct each ofcontrollers 114 (e.g., slave controllers) to control/manage operationsof each correspondingly coupled storage drive 116. For example,controllers 114 may provide information (e.g., storage-drivecharacteristics, performance parameters, or the like) to the masternetwork computer. The master network computer can determinestorage-drive power-up sequences and/or schedules, identifyingpotentially failing storage drives, coordinate backup and/or recovery ofa potentially failing (or already failed) storage drive, or the like, asdescribed herein. Based on these determinations, the master networkcomputer may provide instructions to one or more of controllers 114 formanaging their correspondingly coupled storage drives. For example, themaster network computer may provide separate instructions to eachcontroller, which may separately indicate when and/or how a controlleris to power-up a correspondingly coupled storage drive.

It should be noted that these architectures are not to be construed asexhaustive or limiting, but rather, other architectures may be employedin accordance with embodiments described herein. For example, in variousembodiments, network computers 102-105 and/or controllers 114 mayoperate in various different architectures including, but not limitedto, a peer-to-peer architecture, peer-to-server architecture,server-to-server architecture, or the like, to control/manage theoperations of one or more of storage drives 116. As described herein,the control/management of storage-drive operations may include, but isnot limited to determining storage-drive power-up sequences and/orschedules, identifying potentially failing storage drives, coordinatebackup and/or recovery of a potentially failing (or already failed)storage drive, or the like.

Illustrative Network Computer

FIG. 2 shows one embodiment of a network computer 200 that may includemany more or less components than those shown. The components shown,however, are sufficient to disclose an illustrative embodiment forpracticing the invention. Network computer 200 may represent, forexample network computers 102-105 of FIG. 1, and/or other networkdevices.

Network computer 200 may be configured to operate as a server, client,peer, a host, or other computing device. In general, network computer200 may be a desktop computer, mobile computer (e.g., laptop computers,smart phones, tablets, or the like), server computer, or any othernetwork computer that can communicate through a network to access and/orstore data at a remote/secondary location (i.e., multi-storage-drivechassis 110 of FIG. 1).

Network computer 200 may include processor 202, processor readablestorage media 228, network interface 230, an input/output interface 232,hard disk drive 234, video display adapter 236, and memory 226, all incommunication with each other via bus 238. In some embodiments,processor 202 may include one or more central processing units.

Network interface 230 includes circuitry for coupling network computer200 to one or more networks, and is constructed for use with one or morecommunication protocols and technologies including, but not limited to,protocols and technologies that implement any portion of the OSI model,GSM, CDMA, time division multiple access (TDMA), UDP, TCP/IP, SMS, MMS,GPRS, WAP, UWB, WiMax, SIP/RTP, EDGE, W-CDMA, LTE, UMTS, OFDM, CDMA2000,EV-DO, HSDPA, or any of a variety of other wireless communicationprotocols. Network interface 230 is sometimes known as a transceiver,transceiving device, or network interface card (NIC). In variousembodiments, network interface unit 230 may enable network computer 200to access and/or store data on one or more storage drives associatedwith a multi-storage-drive chassis, such as multi-storage-drive chassis110 of FIG. 1.

Network computer 200 may comprise input/output interface 232 forcommunicating with external devices, such as a keyboard, or other inputor output devices not shown in FIG. 2. Input/output interface 232 canutilize one or more communication technologies, such as Universal SerialBus (USB), infrared, WiFi, WiMax, Bluetooth™, wired technologies, or thelike.

Memory 226 may include various types of storage technologies, which mayinclude various types of non-volatile storage, volatile storage, or acombination thereof. Examples of memory 226 may include, but are notlimited to Random Access Memory (RAM) (e.g., RAM 204), dynamic RAM(DRAM), static RAM (SRAM), Read-only Memory (ROM) (e.g., ROM 222),Electrically Erasable Programmable Read-only Memory (EEPROM), flashmemory, hard disk drives, optical drives, magnetic computer storagedevices, tape drives, floppy disk drives, or other processor-readablestorage media. In some embodiments, memory 226 may includeprocessor-readable transitory or non-transitory storage media. Invarious embodiments, memory 226 may include one or more caches.

Memory 226 may be utilized to store information, such as, but notlimited to, processor-readable instructions (also referred to ascomputer-readable instructions), structured and/or unstructured data,program modules, or other data/information. In various embodiments, someof the data/information stored by memory 226 may be used by processor202 to execute and/or perform actions. In some embodiments, at leastsome of the data/information stored by memory 226 may also be stored onanother component of network computer 200, such as, but not limited to,process-readable storage media 228. Processor-readable storage media 228may include one or more storage technologies, such as, but not limitedto, those storage technologies described above for memory 226. Invarious embodiments, processor-readable storage media 228 may also bereferred to as computer-readable storage media, processor-readablestorage devices, and/or computer-readable storage devices. In someembodiments, process-readable storage media 228 may be removable ornon-removable from network computer 200.

Memory 226 may include system firmware, such as BIOS 224, which maystore instructions for controlling low-level operations of networkcomputer 200. Memory 226 may also store operating system 206 forcontrolling the operation of network computer 200. In some embodiments,operating system 206 may include a general purpose operating system(e.g., UNIX, LINUX™, Windows™, OSX™, Windows Phone™, iOS™, Android™, orthe like). The operating system functionality may be extended by one ormore libraries, modules, plug-ins, or the like.

Memory 226 may include one or more data storage 208, which can beutilized by network computer 200 to store, among other things,applications 214 and/or other data. For example, data storage 208 mayalso be employed to store information that describes variouscapabilities of network computer 200. The information may then beprovided to another device based on any of a variety of events,including being sent as part of a header during a communication, sentupon request, or the like. Data storage 208 may also include a database,text, spreadsheet, folder, file, or the like, that may be configured tomaintain and store user account identifiers, user profiles, emailaddresses, IM addresses, and/or other network addresses; or the like.Data storage 208 may further include program code, data, algorithms, andthe like, for use by a processor, such as processor 202 to execute andperform actions. In one embodiment, at least some of data store 208might also be stored on another component of network computer 200,including, but not limited to processor-readable storage media 228, harddisk drive 234, or the like.

Applications 214 may include computer executable instructions that, whenexecuted by network computer 200, transmit, receive, and/or otherwiseprocess instructions and data. Examples of application programs mayinclude, but are not limited to, calendars, search programs, emailclient applications, IM applications, SMS applications, contactmanagers, task managers, transcoders, schedulers, database programs,word processing programs, encryption applications, securityapplications, spreadsheet applications, games, and so forth.

A mobile computer may include a browser application that is configuredto receive and to send web pages, web-based messages, graphics, text,multimedia, and the like. The mobile computer's browser application mayemploy virtually any programming language, including a wirelessapplication protocol messages (WAP), and the like. In at least oneembodiment, the browser application is enabled to employ Handheld DeviceMarkup Language (HDML), Wireless Markup Language (WML), WMLScript,JavaScript, Standard Generalized Markup Language (SGML), HyperTextMarkup Language (HTML), eXtensible Markup Language (XML), HTML5, and thelike.

Applications 214 may also include an application that can enable a userto individually access each separate controller (e.g., controllers 114of FIG. 1) associated with each storage drive (e.g., storage drives 116of FIG. 1) through a network. So, in some embodiments, each controller(i.e., each storage drive) may be individually network addressable bynetwork computer 200. This access can enable a user to employ control(e.g., power/voltage changes, temperature and other drive performancemonitoring, or the like) over each individual drives within amulti-storage-drive chassis.

In various embodiments, network computer 200 may operate as a masternetwork computer to cooperatively coordinate with at least one ofcontrollers (e.g., controllers 114 of FIG. 1) to control/manageoperations of one or more storage drives coupled to the controllers. Inat least one such embodiment, network computer 200 may perform at leasta portion of the operations described herein.

Illustrative Wireless Controller Computer

FIG. 3A shows one embodiment of wireless controller 340 that may includemany more or less components than those shown. The components shown,however, are sufficient to disclose an illustrative embodiment forpracticing the invention. Wireless controller 340 may represent, forexample controllers 114 of FIG. 1.

Controller 340 may be configured to enable individualized communicationbetween a single storage drive (e.g., storage drives 116 of FIG. 1) andone or more network devices (e.g., network computers 102-105 of FIG. 1).It should be understood that although a single controllermanages/controls a single storage drive, a plurality of controllers canwork together to provide centralized management of a plurality ofstorage drives.

Controller 340 may include processor 302, first connector 330, secondconnector 332, and memory 304, all in communication with each other viabus 328. In some embodiments, processor 302 may include one or morecentral processing units. First connector 330 may be a connectorconfigured to couple with and/or accept a storage-drive connector. In atleast one embodiment, first connector 330 may be a SATAconnector—although other storage-drive-compatible connectors may beutilized, as described herein. Wireless interface 334 may include one ormore antennas for communicating wireless signals with one or more otherwireless controllers or one or more Radio Adapters. The wirelesscommunication signals may be communicated with a standard wirelessprotocol, modified standard wireless protocol, and/or a proprietarywireless protocol.

Memory 304 may include various types of storage technologies, which mayinclude various types of non-volatile storage, volatile storage, or acombination thereof. Examples of memory 304 may include, but are notlimited to Random Access Memory (RAM), dynamic RAM (DRAM), static RAM(SRAM), Read-only Memory (ROM), (Electrically Erasable ProgrammableRead-only Memory (EEPROM), flash memory, or other processor-readablestorage media. In some embodiments, memory 304 may includeprocessor-readable transitory or non-transitory storage media. Invarious embodiments, memory 304 may include one or more caches.

Memory 304 may be utilized to store information, such as, but notlimited to, processor-readable instructions (also referred to ascomputer-readable instructions), structured and/or unstructured data,program modules, or other data/information. In various embodiments, someof the data/information stored by memory 304 may be used by processor302 to execute and/or perform actions.

Memory 304 may include system firmware, such as BIOS 308, which maystore instructions for controlling low-level operations of controller340. Memory 304 may also store operating system 306 for controlling theoperation of controller 340. In some embodiments, operating system 306may include a general purpose operating system (e.g., UNIX, LINUX™, orthe like) or a customized operating system. The operating systemfunctionality may be extended by one or more libraries, modules,plug-ins, or the like.

Memory 304 may include one or more data storage 310, which can beutilized by controller 300 to store, among other things, applications320 and/or other data. Data storage 310 may further include programcode, data, algorithms, and the like, for use by a processor, such asprocessor 302 to execute and Data storage 310 may be employed to storeinformation associated with a storage drive that is connected tocontroller 340, such as, for example, a history of temperatures,voltages, utilization, or the like. Memory 304 may also be utilized tostore network traffic information to enable communication with otherdevices, such as network computers 102-105 of FIG. 1 or othercontrollers (e.g., controllers 114 of FIG. 1). Applications 320 mayinclude various applications for managing a storage drive, including,for example, power scheduling/management, diagnostic recording andassessment tools, or the like. In any event, controller 340 may beconfigured to employ various embodiments, combinations of embodiments,processes, or parts of processes, as described herein.

Illustrative Radio Adapter Computer

FIG. 3B shows one embodiment of radio adapter 350 that may include manymore or less components than those shown. The components shown, however,are sufficient to disclose an illustrative embodiment for practicing theinvention. Radio Adapter 350 may represent, for example Radio Adapter634 of FIG. 6B.

Radio Adapter 350 may be configured to enable individualizedcommunication between wireless controller 340 and one or more networkdevices (e.g., network computers 102-105 of FIG. 1). It should beunderstood that although a single radio adapter may be employed, aplurality of radio adapters can work together to provide redundancy andflexible bandwidth to access a plurality of storage drives.

Radio adapter 350 may include processor 352, first connector 366,wireless interface 368, and memory 354, all in communication with eachother via bus 364. In some embodiments, processor 352 may include one ormore central processing units. First connector 366 may be a connectorconfigured to couple to a remote network via a high bandwidthconnection. An external communication interface of radio adapter 250 mayinclude first connector 366. In at least one embodiment, first connector366 may be a fiber optic connector—although other high bandwidthconnectors may be utilized. Wireless interface 368 may include one ormore antennas for communicating wireless signals with one or morewireless controllers and/or one or more other Radio Adapters. Thewireless communication signals may be communicated with a standardwireless protocol, modified standard wireless protocol, and/or aproprietary wireless protocol.

Memory 354 may include various types of storage technologies, which mayinclude various types of non-volatile storage, volatile storage, or acombination thereof. Examples of memory 354 may include, but are notlimited to Random Access Memory (RAM), dynamic RAM (DRAM), static RAM(SRAM), Read-only Memory (ROM), Electrically Erasable ProgrammableRead-only Memory (EEPROM), flash memory, or other processor-readablestorage media. In some embodiments, memory 354 may includeprocessor-readable transitory or non-transitory storage media. Invarious embodiments, memory 354 may include one or more caches.

Memory 354 may be utilized to store information, such as, but notlimited to, processor-readable instructions (also referred to ascomputer-readable instructions), structured and/or unstructured data,program modules, or other data/information. In various embodiments, someof the data/information stored by memory 354 may be used by processor352 to execute and/or perform actions.

Memory 354 may include system firmware, such as BIOS 358, which maystore instructions for controlling low-level operations of radio adapter350. Memory 354 may also store operating system 356 for controlling theoperation of radio adapter 350. In some embodiments, operating system356 may include a general purpose operating system (e.g., UNIX, LINUX™,or the like) or a customized operating system. The operating systemfunctionality may be extended by one or more libraries, modules,plug-ins, or the like.

Memory 354 may include one or more data storage 360, which can beutilized by controller 300 to store, among other things, applications362 and/or other data. Data storage 360 may further include programcode, data, algorithms, and the like, for use by a processor, such asprocessor 352 to execute and Data storage 360 may be employed to storeinformation associated with accessing a network and/or a network devicethat is remote, managing communication with one or more wirelesscontrollers, and managing communication with one or more other radioadapters. Memory 354 may also be utilized to store network trafficinformation to enable communication with other devices, such as networkcomputers 102-105 of FIG. 1 or other radio adapters and wirelesscontrollers. Applications 362 may include various applications formanaging communication, or the like. In any event, radio adapter 350 maybe configured to employ various embodiments, combinations ofembodiments, processes, or parts of processes, as described herein.

Illustrative Wireless Data Storage Chassis

FIG. 4 illustrates an exploded perspective view of a wirelessmulti-storage-drive chassis, a storage-drive carrier, a storage drive, aradio adapter, a waveguide, and a wireless controller in accordance withembodiments described herein. System 420 may include wirelessmulti-storage-drive chassis 430 and storage-drive carrier 424. Wirelessmulti-storage drive chassis 430 may be an example of a JBOD or otherchassis that can support a plurality of storage drives. In variousembodiments, multi-storage-drive chassis 430 may include one or moreradio adapters 432 and waveguide 434. In various embodiments, the radioadapters may provide communication between wireless controllers and/orfrom the chassis to other networks.

In some embodiments, storage-drive carrier 424 may be an embodiment of astorage-drive carrier disclosed in U.S. patent application Ser. No.14/596,179 filed on Jan. 13, 2015, entitled “NETWORK AQDDRESSABLESTORAGE CONTROLLER WITH STORAGE DRIVE PROFILE COMPARISON,” which isincorporated by reference in its entirety. Wireless controller 426 maybe embodiment of wireless controller 340 of FIG. 3A. As illustrated,wireless controller 426 may be coupled to a back of storage drive 422.This combination of devices may be fastened to storage drive carrier424. The combined carrier 424, drive 422, and wireless controller 426may be inserted into slot 428 of chassis 430 in accordance with useinstructions of chassis 430 for inserting a carrier into slot 428. Onceinserted, wireless controller 426 may wirelessly communicate via achannel in waveguide 434 with radio adapter 432 and other wirelesscontrollers and/or radio adapters coupled to waveguide 434.

FIG. 5 illustrates an exploded perspective view of another embodiment ofa wireless chassis that includes a waveguide bisected by a terminationplate and two radio adapters electromagnetically isolated from oneanother by the termination plate, in accordance with embodimentsdescribed herein. System 520 includes wireless multi-storage-drivechassis 530. In various embodiments, wireless chassis 530 includes aplurality of shelves, such as a lowermost shelf 540 and an uppermostshelf. As shown, the plurality of shelves are preferably distributedalong a substantially vertical direction. As discussed further below,each of the plurality of shelves may be configured and arranged toreceive one or more storage drives, such as first storage drive 522 orsecond storage drive 572, and corresponding wireless controllers, suchas first wireless controller 526 or second wireless controller 576.

System 520 includes a first storage-drive carrier 524, the first storagedrive 522, and a first wireless controller 526 received in a first slot528. As shown, the first slot may be positioned within a shelf, such asuppermost shelf 542. As discussed in greater detail throughout,including at least in the context of FIGS. 7 and 8, each shelf may beconfigured and arranged to receive a plurality of tiled configurations,wherein each tiled configuration includes a plurality of storage drivesand corresponding wireless controllers. For instance, as shown in apreferred, but non-limiting embodiment, in FIG. 7, tiled configuration700 includes four storage drives and a corresponding wireless controllerfor each of the four storage drives.

Referring back to FIG. 5, system 520 includes a second storage-drivecarrier 574, a second storage drive 572, and a second wirelesscontroller 576 received in a second slot 578 positioned within thelowermost shelf 540. Second slot 578 is vertically below first slot 528.Although now shown, storage drives and corresponding wirelesscontrollers may be positioned in the other shelves between the lowermostshelf 540 and the uppermost shelf 542.

System 520 also includes a first radio adapter 532, a second radioadapter 582, and a waveguide 534. Waveguide 534 is bisected by atermination plate 550 to form a first waveguide portion 536 and a secondwaveguide portion 586. The first waveguide portion 536 is verticallyabove the termination plate 550 and the second waveguide portion 586 isvertically below the termination plate 550. Accordingly, the terminationplate 550 electromagnetically isolates the first waveguide portion 536from the second waveguide portion 586. The termination plate 550 haseffectively multiplexed the geometry of chassis 530 by subdividingwaveguide 534 into separate and distinct waveguides 534/586. Each ofwaveguide or electromagnetically isolated waveguide portions thatoperative to transmit separate and distinct wireless signalssimultaneously, increasing a total communication bandwidth of chassis530.

Although not shown, wireless chassis may include additional waveguidesthat are substantially vertical waveguides and also bisected bytermination plate 550, further multiplexing the geometry of chassis 530.In addition to isolating waveguide portions, termination plate 550prevents reflections and standing waves of wireless communicationsignals within each of the isolated waveguide portions 536 and 586. Inat least one embodiment, a terminating structure, such as a conductor,is placed internal to the cavity and along the length of waveguide 534.Such a structure is configured and arranged to subdivide the cavity ofwaveguide 534 into separate and distinct waveguide channels orairspaces, providing further multiplexing of the geometry and enhancingthe communication bandwidth of chassis 530.

First wireless controller 526 is operative to wirelessly communicate,via the first waveguide portion 536, with the first radio adapter 532and other wireless controllers and/or radio adapters electromagneticallycoupled to the first waveguide portion 536. For instance, first wirelesscontroller 526 may communicate with other wireless controllerspositioned on any shelf that is vertically above termination plate 550and communicatively coupled to at least one of first waveguide portion536 or first radio adapter 532.

Likewise, second wireless controller 576 is operative to wirelesslycommunicate, via the second waveguide portion 586, with the second radioadapter 582 and other wireless controllers and/or radio adapterselectromagnetically coupled to the second waveguide portion 586. Notethat due to the termination plate 550, first and second wirelesscontrollers 526/576 cannot directly wirelessly communicate with eachother via waveguide 534. Rather, the first and second controllers526/576 may communicate via another communication route, such as, butnot limited to, a wired connection between first and second radioadapters 532/582.

FIG. 6 shows a schematic view of a wireless communication system thatincludes a plurality of storage drives, corresponding wirelesscontrollers, and a radio adapter electromagnetically coupled via awaveguide. Chassis portion 620 includes a plurality of non-specificstorage drives 622 and a corresponding plurality of wireless controllers626. Each of the plurality of wireless controllers 626 iscommunicatively coupled to and controls the corresponding storage drive622. Furthermore, each of the wireless controllers 626 includes at leasta first wireless interface that is electromagnetically coupled towaveguide 634. In various embodiments, each of the wireless interfacesincludes one or more antennas that is configured and arranged totransmit and receive wireless signals via waveguide 634.

Chassis portion 620 additionally includes one or more radio adaptors,such as radio adapter 632. Radio adaptor 632 is electromagneticallycoupled to waveguide 634 via a wireless interface. For instance, radioadapter 632 includes one or more antennas that are positioned totransmit and receive wireless signals via waveguide 634. In a preferredembodiment, radio adapter 632 includes at least a first connector thatis enabled to transmit and receive signals to and from another networkdevice over a network, such as through an Ethernet protocol. Theplurality of signals 640 schematically represents the transmission, viawaveguide 634, of wireless signals between various pairs of the wirelesscontrollers 626 and between the wireless controllers 626 and the radioadapter 632.

FIG. 7 shows a front schematic view of one embodiment of a tiledconfiguration of a plurality of non-specific storage drives andcorresponding wireless controllers electromagnetically coupled to avertical waveguide. The tiled configuration, or simply tile 700,includes a plurality of storage drives and a corresponding plurality ofwireless controllers. Specifically, tile 700 includes N storage drivesand N wireless controllers, where N is a positive integer. In thepreferred embodiment shown in FIG. 7, N=4, however it should beunderstood that in other embodiments N may be greater or less than four.

In various embodiments, the plurality of storage drives and wirelesscontrollers are provided power through a connection to the backplane ofa chassis, as discussed throughout. Furthermore, the wireless interfacesinclude an antenna routing that provides at least one antenna for eachof the wireless controllers' access to waveguide 734. At least one ofthe power distribution or antenna routing may be at least partiallyenabled by flex circuit components. For instance, thetransmitting/receiving antennas may be printed on a flexible circuitthat is operative to extend into the cavity of waveguide 734. Waveguide734 includes a port or inlet 736 to provide the antennas of the wirelesscontrollers access to the transmitting cavity or airspace of waveguide734. Note that each of the plurality of wireless controllers of tile 700is provided access to waveguide 734 via the common port 736. In variousembodiments, waveguide 734 is configured and arranged to transmitwireless signals, such as RF signals, along a substantially verticaldirection.

FIG. 8A shows top, front, and side schematic views of an exemplary, butnon-limiting embodiment of a wireless data storage chassis shelfpopulated with a plurality of storage drives (“SD”) and correspondingwireless controllers (“WC”). Shelf 800 may be similar to uppermost shelf542 or lowermost shelf 540 of chassis 530 of FIG. 5. From the top viewof shelf 800, a plurality of wireless controllers are visible. The frontand side views show the vertical stacking of the corresponding pairs ofstorage drives and wireless controllers. As shown in FIG. 8A, thestorage drives and wireless controllers are arranged in a tiledconfiguration, including at least a first tile 810 and second tile 820.Each tile includes a plurality of storage drives and correspondingwireless controllers. Each one of the tiled configurations, includingfirst and second tiles 810/820 may be similar to tile 700 of FIG. 7. Assuch, each tile shown in FIG. 8 includes N=4 storage drive and wirelesscontroller pairs, although other embodiments are not so limited. Forinstance, in other embodiments, N for each tile may be greater or lessthan four.

Furthermore, a plurality of waveguides, including a first waveguide 830(GUIDE_1) and a second waveguide 840 (GUIDE_2) pass through shelf 800.The plurality of waveguides are configured and arranged to transmitwireless communication signals in a direction that is substantiallyorthogonal to a plane defined by shelf 800 (and by page of FIG. 8A).Each of the wireless controllers of each tile is electromagneticallycoupled to one of the waveguides. Thus, in a similar manner to tile 700and waveguide 734 of FIG. 7, each of wireless controllers in each of thetiles is operative to transmit and receive wireless communicationsignals along one of the waveguides that pass through shelf 800.

Each tile is electromagnetically coupled to one of the waveguides. Forinstance, each tile may include a flexible circuit element that ispositioned or otherwise received by a port in a waveguide. The portprovides the wireless controllers of the tile access to the internalcavity of a waveguide. In a preferred embodiment, the number of tiles inshelf 800 is equivalent to the number of waveguides that pass throughshelf 800, such that there is a one-to-one mapping or correspondence forthe electromagnetically coupling of the tiles to the waveguides.

The tiles are arranged in a two dimensional array within shelf 800. Thetwo-dimensional array may be an m×n array of tiles, where each of m andn are positive integers. In the embodiment shown in FIG. 8A, eachalternating column of the m×n array is offset or staggered. Otherembodiments are not so constrained, and the tiles may be organized inany suitable structure. In preferred embodiments, there are m×nwaveguides passing through a shelf, one for each of a correspondingtiles. As described in greater detail below, multiple waveguides withina chassis enable the multiplexing of the geometry of the chassis,resulting in an enhanced bandwidth. In the embodiment shown in FIG. 8A,m=6 and n=3. There are 6×3=18 tiles positioned in shelf 800. There arealso 18 separate and distinct waveguides passing through shelf 800.Furthermore, shelf 800 includes N×(m×n)=72 pairs of storage drives andwireless controllers. For a chassis that includes X shelves, the chassismay house X×(m×n) tiles or X×(N×(m×n)) storage drives/wirelesscontroller pairs, where X is a positive integer. Other embodiments arenot so constrained, and each of X, N, m and n may be virtually anypositive integer.

The number of waveguides passing through a shelf scales with the numbertiles positionable within the shelf. For instance, in a preferredembodiment, a chassis includes Y×(m×n) waveguides or separate anddistinct wave guide portions, where Y is a positive integer based on ageometrical multiplexing factor. For instance, when a termination platesubdivides a single waveguide into separate and distinct portions, suchas termination plate 550 of FIG. 5 or termination plate 1048 of FIG.10C, Y=2, because the termination plate has resulted in twice as manyseparate and distinct (i.e. electromagnetically isolated) multiplexedwaveguide portions.

The four wireless controllers included in first tile 810 are notated as:WC_1_1, WC_1_2, WC_1_3, and WC_1_4. In the notation WC_i_j, the firstindex (i) indicates the tile index and the second index (j) indicatesthe wireless controller index for the tile. Likewise, the four storagedrives of first tile 810 are notated as: SD_1_1, SD_1_2, SD_1_3, andSD_1_4. The wireless interfaces for each of the wireless controllersincluded in first tile 810 are configured and arranged to transmit andreceive wireless communication signals along the first waveguide 830,which is notated as GUIDE_1, where the integer index indicates thecorresponding tile index. Thus, the first waveguide 830 is common toeach of the wireless controllers of first tile 810.

Likewise, second tile 820 includes four wireless controllers: WC_2_1,WC_2_2, WC_2_3, and WC_2_4 and four storage devices: SD_2_1, SD_2_2,SD_2_3, and SD_2_4. The wireless interfaces for each of the wirelesscontrollers included in second tile 820 are configured and arranged totransmit and receive wireless communication signals along the secondwaveguide 840 (GUIDE_2). Thus, the second waveguide 840 is common toeach of the wireless controllers of second tile 820. As shown in FIG.8A, each of tiles and corresponding common waveguides are notated usingsimilar nomenclature. As discussed herein, each of the wirelesscontrollers in a tile is electromagnetically coupled to a particularwaveguide and are operative to wirelessly communicate with otherwireless controllers of corresponding tiles populating other shelves ina chassis, where the corresponding tiles are also electromagneticallycoupled to the particular waveguide. In various embodiments, at leastthe wireless controllers and the storage drives are provided power via abackplane of shelf 800, as shown in FIG. 8A.

FIG. 8B shows a schematic view of a wireless chassis where a pluralityof waveguides communicatively couple corresponding storage drivecontrollers across a plurality of vertically stacked chassis shelves.Wireless chassis 850 includes a housing 852 to house devices, such asstorage drives, wireless controllers, radio adapters, power supplies,waveguides, and the like. Wireless chassis 850 further includes a firstshelf 860, a second shelf 870, and a third shelf 880. Each of shelves860/870/890 may be similar and include more or less features than shelf800 of FIG. 8A. In other embodiments, wireless chassis 850 includes moreor less shelves.

Furthermore, wireless chassis 850 includes a first waveguide 892, asecond waveguide 894, and a third waveguide 896. Each of waveguides 892,894, and 896 is terminated from above and below by an upper terminationplate 888 and a lower termination plate 898 respectively. Otherembodiments include fewer or more than three waveguides, as well asfewer than or more than two termination plates. For instance, as shownin FIG. 8A, 18 separate and distinct waveguides pass through shelf 800.Also, another termination plate may be positioned verticallyintermediate the upper and lower termination plates 888/898 to subdivideat least one of the waveguides 892/894/896 into electromagneticallyisolated waveguide portions. Each waveguide 892/894/896 passes througheach of shelves 860/870/880.

A radio adapter 890 is electromagnetically coupled to each of firstwaveguide 892, second waveguide 894, and third waveguide 896. Suchcoupling is schematically represented by an antenna included a wirelessinterface of radio adapter positioned to receive and transmit wirelesscommunication signals within each of waveguides 892/894/896. Radioadapter 890 includes a first connector, or at least a remotecommunication interface, that is operative to communicate to networkdevices over a network. The first connector is schematically representedas an Ethernet connection. In at least one embodiment, radio adapter 890is operative to wirelessly communicate with network devices, exterior tothe chassis 890.

First shelf 860 includes three tiled configurations of storage devices(SD) and corresponding wireless controllers (WC): tiles 862, 864, and866. As discussed throughout, in other embodiments, a shelf may includemore or less than three tiles. For instance, shelf 800 of FIG. 8A ispopulated with 18 tiles. Likewise, second shelf 879 is populated withthree tiles 872/874/876 and third shelf 880 is populated with threeother tiles 882/884/886. Each of the tiles included in the shelves maybe similar to and include more or less features than tile 700 of FIG. 7.

Each of tiles 862, 872, and 882 are electromagnetically coupled to firstwaveguide 892, via ports in waveguide 892. Such coupling isschematically represented by an antenna (included in the correspondingwireless interface) for each of the wireless controllers in each oftiles 862/872/882 positioned to receive and transmit wirelesscommunication signals within first waveguide 892. Each of the wirelesscontrollers in each of tiles 862, 872, and 882 is operative towirelessly communicate with each of the other wireless controllers oftiles 862, 872, and 882, as well as radio adapter 890, via firstwaveguide 892.

Similarly, each of tiles 864, 874, and 884 are electromagneticallycoupled to second waveguide 894. Thus, any wireless controller of tiles864, 874, and 884 can wirelessly communicate to any other wirelesscontroller of tiles 864, 874, and 884, as well as radio adapter 890 viasecond waveguide 894. Each of tiles 866, 876, and 886 areelectromagnetically coupled to third waveguide 896 and are operative towirelessly communicate with any other device electromagnetically coupledto third waveguide 896. If should be noted that tileselectromagnetically coupled to separate and distinct waveguides orwaveguide portions are operative to wirelessly communicate via radioadapter 890 because radio adapter 890 is common to each of thewaveguides 892, 894, and 896.

FIG. 9A shows a schematic view of an embodiment of a mating or couplingsurface of radio adapter that is operative to electromagnetically coupleto a plurality of waveguides included in a wireless chassis. The matingsurface of radio adapter, as shown in FIG. 9A is configured and arrangedto mate to a plurality of waveguides within a wireless chassis.Specifically, radio adapter 990 communicatively couples to thewaveguides passing through shelf 800 of FIG. 8A by the mating surfacemating with terminal ends of the waveguides.

Radio adapter 990 includes a plurality of channel elements, including atleast a first channel element 932 and a second channel 942, where areschematically represented in FIG. 9A to each include four antennas. Theplurality of channel elements are arranged in a staggered m×n array,similar to the staggered array of tiles and waveguides of shelf 800 ofFIG. 8A. Note the geometry of the staggered array corresponds to thestaggering of the waveguides in shelf 800. Accordingly, the matingsurface of radio adapter 990 corresponds to the tiled configuration andwaveguide configuration of a plurality of shelves included in a wirelesschassis.

Each of the plurality of channel elements is operative toelectromagnetically couple to a terminal end of a single waveguideincluded in the wireless chassis. Each of the channel elements mayinclude a portion of the one or more wireless interfaces of radioadapter 990. Via the plurality of channel elements, radio adapter 990 isoperative to wirelessly communicate along a plurality of waveguides, ina similar manner that radio adapter 890 of FIG. 8B is common to, andoperative to wirelessly communicate to other devices electromagneticallycoupled to any of waveguides 892, 894, and 896.

As such, each of the channel elements is operative employ one or moreantennas to transmit and receive wireless signals along the waveguidethat is electromagnetically coupled to the particular channel element.As shown in the embodiment of FIG. 9A, each of the channel elementsemploy one or more separate and distinct antennas. However, it should beunderstood that other embodiments are not so limited and each of thechannel elements may employ more than or less than four antennas towirelessly communicate along each of a plurality of waveguides.

As noted above, radio adapter 990 is configured and arranged for awireless chassis that includes one or more shelves similar to shelf 800of FIG. 8A. Because there are 18 waveguides passing through shelf 800,radio adapter 990 includes 18 channel elements; one channel element foreach of the waveguides passing through shelf 800. First channel element932 is operative to electromagnetically couple to first waveguide 830 ofFIG. 8A and second channel element 942 is operative toelectromagnetically couple to second waveguide 840 of FIG. 8A. Each ofthe other channel elements of radio adapter 990 is operative to coupleto one of the other waveguides passing through shelf 800 of FIG. 8A. Itshould be understood that radio adapter 990 is a non-limitingembodiment, and other configurations are possible so that less than ormore than 18 wireless interfaces are included in a single radio adapter.

FIG. 9B shows a schematic view of the plurality of channel elementsincluded in a radio adapter. In various embodiments of radio adapter 990of FIG. 9B, radio adapter 990 includes a plurality of channel elements,including first channel element 932 and second channel element 942 thatprovide interfaces to a plurality of waveguides that geometricallymultiplex a wireless chassis. In at least one embodiment, a wirelessprotocol to Ethernet protocol translation is performed by each of thechannel elements. In other embodiments, the wireless protocol toEthernet protocol translation for each of the channel elements isperformed by another component of radio adapter 990.

FIG. 10A shows a front view of an embodiment of a wireless data storagechassis that is consistent with the various embodiments disclosedherein. Chassis 1000 includes a plurality of vertically stacked shelves1010. In the embodiment shown in FIG. 10A, chassis 1000 includes tenshelves 1010, but it should be understood that other embodiments includemore or less than 10 shelves. Each of the plurality of shelves mayreceive a plurality of storage drives and corresponding wirelesscontroller. In at least one embodiment, each shelve may receive aplurality of tiles, such as tile 700 of FIG. 7. In some embodiments,each shelf may be similar, or at least include similar features to shelf800 of FIG. 8A.

Chassis 1000 includes a plurality of waveguides 1002. The waveguides maybe arranged in a two dimensional staggered or non-staggered m×n array.In the embodiment shown in FIG. 10A, m=6 and n=3, although each of m andn may be any positive integer. Accordingly, chassis 1000 includes 18waveguides. Because FIG. 10A shows a front view of chassis 1000, onlythree of the 18 waveguides are visible. As shown, each of the pluralityof waveguides 1002 is substantially a vertical waveguide and passesthrough each of the plurality of vertically stacked shelves 1010. In apreferred embodiment, each of the plurality of shelves is populated atwo dimensional array of tiles, wherein each tile is electromagneticallycoupled to one of the plurality of waveguides, as shown in chassis 850in FIG. 8B. Each of the waveguides is terminated by a termination plate1006. In various embodiments, the plurality of storage drives at leastpartially surround each of the plurality of waveguides 1002. Thestorage-drive carries, such as storage drive carrier 524 of FIG. 5, mayat least provide some RF-shielding or a Faraday cage-like effect toshield the signals within the plurality of waveguides 1002. The housingof chassis 1000 may provide additional shielding. Accordingly, thewireless signals transmitted along the waveguides 1002 may not bedetectable or otherwise intercepted from outside chassis.

Chassis 1000 includes a radio adapter 1004. The plurality of waveguides1002 and the radio adapter 1004 enable a wireless communication betweeneach of the wireless controllers that are received by the plurality ofshelves 1010. In various embodiments, a mating surface of radio adapter1994, such as the mating surface of radio adapter 990 of FIG. 9A isconfigured and arrange to mate with the ends of the waveguides 1002.

FIG. 10B shows a front view of an embodiment of a redundant wirelessdata storage chassis that is consistent with the various embodimentsdisclosed herein. Chassis 1020 may include similar features to thoseincluded in chassis 1000 of FIG. 10A. Furthermore, chassis 1020 mayinclude more or less features than those included in chassis 1000. Forinstance, chassis 1020 includes a plurality of waveguides 1022 that passthrough a plurality of shelves 1030. Chassis 1020 includes two radioadapters: an upper radio adapter 1024 and a lower radio adapter 1026.The upper/lower or first/second radio adapters 1024/1026 may beredundant radio adapters, such that if the operation of one of the radioadapters 1024/1026 were to be interrupted or if a radio adapter1024/1026 were to malfunction or become damaged, the operation ofwireless chassis 1020 would not be interrupted. Accordingly, chassis1020 is a redundant wireless chassis.

FIG. 10C shows a front view of an embodiment of a geometricallymultiplexed wireless data storage chassis that is consistent with thevarious embodiments disclosed herein. Chassis 1040 may include similarfeatures to those included in chassis 1020 of FIG. 10B or chassis 1000of FIG. 10A. Furthermore, chassis 1040 may include more or less featuresthan those included in either of chassis 1020 or chassis 1000. Forinstance, chassis 1040 includes a plurality of waveguides 1042 that passthrough a plurality of shelves 1050. Chassis 1040 includes two radioadapters: an upper radio adapter 1044 and a lower radio adapter 1046.

A termination plate 1048 subdivides each of the plurality of waveguides1042 into two portions: an upper portion and a lower portion.Termination plate 1048 electromagnetically isolates the upper portionsof each waveguide from the lower portion of the waveguide. In a similarmanner as the first radio adapter 532 of FIG. 5 is communicativelycoupled to the upper portion of waveguide 534 of FIG. 5, the upper radioadapter 1044 is electromagnetically coupled to the upper portions ofeach of the plurality of waveguides 1042. Likewise, the lower radioadapter 1046 is electromagnetically coupled to the lower portions ofeach of the plurality of waveguides 1042. Accordingly, each of the tilesin shelves that are above termination plate 1048 are operative towirelessly communicate with the other tiles in the upper shelves andupper radio adapter 1044. Likewise, each of the tiles in shelves thatare below termination plate 1048 are operative to wirelessly communicatewith the other tiles in the lower shelves and lower radio adapter 1046.Thus, the geometry of the plurality waveguides 1042 is multiplexed.Accordingly, chassis 1040 is a geometrically multiplexed wireless datastorage chassis.

FIG. 10D shows a front view of an embodiment of a geometricallymultiplexed and redundant wireless data storage chassis that isconsistent with the various embodiments disclosed herein. Chassis 1060may include similar features to those included in chassis 1040 of FIG.10C, chassis 1020 of FIG. 10B, or chassis 1000 of FIG. 10A. Furthermore,chassis 1060 may include more or less features than those included in atleast one of chassis 1040, chassis 1020, or chassis 1000. For instance,chassis 1060 includes a plurality of waveguides 1062 that pass through aplurality of shelves 1070. Chassis 1060 includes two radio adapters: anupper radio adapter 1064 and a lower radio adapter 1066.

A termination plate 1068 subdivides each of the plurality of waveguides1062 into two portions: an upper portion and a lower portion. The upperradio adapter 1064 is electromagnetically coupled to the upper portionsof each of the plurality of waveguides 1062. Likewise, the lower radioadapter 1066 is electromagnetically coupled to the lower portions ofeach of the plurality of waveguides 1062. Chassis 1060 is ageometrically multiplexed wireless data storage chassis.

Chassis 1060 also includes a dual radio adapter 1072 that iselectromagnetically coupled to the upper and lower portions of thesubdivided plurality of waveguides 1062. Thus, dual radio adapter spanstermination plate 1068. Dual radio adapter 1072 includes a first radioadapter 1074 that is operative to transmit and receive wirelesscommunication signals in the upper portion of the plurality ofwaveguides 1062. Dual radio adapter 1072 also includes a second radioadapter 1074 that is operative to transmit and receive wirelesscommunication signals in the lower portion of the plurality ofwaveguides 1062. In a preferred embodiment, the first radio adapter 1074of dual radio adapter 1072 is communicatively coupled to the secondradio adapter 1076 of dual radio adapter 1072. Chassis 1060 is aredundant chassis because if the operation of one of the radio adaptersis interrupted, the operation of chassis 1060 will not be interrupted.

Multiplexing a Bandwidth of a Wireless Data Storage Chassis

FIG. 11 illustrates a logical flow diagram generally showing anembodiment of a process for multiplexing, increasing, or otherwiseenhancing a bandwidth of a wireless data storage chassis. Process 1100may begin, after a start block, at block 1102, where a frequency spacewithin the volume of a chassis is multiplexed. Multiplexing frequencyspaces are discussed in greater detail in regards to FIGS. 12A-12B.Process 1100 may proceed to block 1104, where an airspace within thevolume of a chassis is multiplexed. Multiplexing an airspace isdiscussed in greater detail in regards to FIGS. 13-15B. Process 1100 mayproceed next to block 1006, where the geometry of the chassis ismultiplexed.

Many wireless protocols, such as, but not limited to WiFi (IEEE 802.11),Bluetooth (IEEE 802.15.1), WiMax (IEEE 802.16), WiMax MIMO, WiMax MISO,ZigBee (IEEE 802.15.4), MiWi (IEEE 802.15.4), and the like providestandards for various embodiments of multiplexing a frequency space.However, briefly FIG. 12A illustrates a logical flow diagram generallyshowing an embodiment of a process for multiplexing a frequency spacewithin a volume of a chassis when wirelessly transmitting data. Process1200 may begin, after a start block, at block 1202, where at least aportion of a frequency band is subdivided into a plurality of frequencychannels.

For an exemplary, but non-limiting embodiment, the IEEE 802.11ac is awireless communication standard for communication in the 5 GHz band andprovides standards for multiplexing the frequency band into a pluralityof frequency channels. Depending on the specific Modulation and CodingScheme (MCS) index chosen, the 5 GHz bands is subdivided into aplurality frequency channels. For instance, the 5 GHz band may besubdivided into frequency channels that are at least one of 20 MHz, 40MHz, 80 MHz, or 160 MHz wide. The total number of frequency channelsdepends on the width of each channel.

Process 1200 may proceed to next to block 1204, where a guard intervalis provided between each pair of adjacent frequency channels. Forinstance, depending on the MCS index chosen, guard intervals of a widthof 400 ns or 800 ns are provided between adjacent frequency channels.

Process 1200 proceeds to block 1206, where an error correction code isgenerated. The generated error correction code is based on the data tobe transmitted. At block 1208, a plurality of signals in one or more ofthe frequency channels is modulated. Modulating the signals is based onat least the data to be transmitted and the error correction code.Various modulating schemes may be employed to modulate the plurality ofsignals. For instance, the 802.11ac protocol employs at least one ofBPSK, QPSK, or 16-/64-/256-QAM modulation, depending on the MCS indexchosen.

Process 1200 proceeds to block 1210, where the modulated plurality ofsignals are wirelessly transmitted in one or more of the frequencychannels. For instance, the plurality of signals may be transmittedalong a waveguide as discussed herein. In various embodiments, at leastone of a wireless controller or a radio adapter transmits the signalsalong a wireless waveguide. After block 1210, process 1200 may return toa calling process to perform other actions. Although the IEEE 802.11acstandard is discussed herein, it is understood that any other process tomultiplex a frequency space may be employed, such as, but not limited toIEEE 802.11ad.

FIG. 12B illustrates a logical flow diagram generally showing anembodiment of a process for multiplexing a frequency within a volume ofa chassis when wirelessly receiving data. Process 1250 may begin, aftera start block, at block 1252, where a plurality of modulated signals inone or more frequency channels is wirelessly received. For instance, thesignals may be received within a waveguide in a wireless chassis. Atleast one of a radio adapter or a wireless controller may receive thesignals within the waveguide. In at least one embodiment, the receivedsignals are the signals that were transmitted at block 1210 of process1200 of FIG. 12A.

At block 1254, the received signals are demodulated based on the MCSindex. At block 1256, the data is determined based on the demodulatedsignals. An error correction code may also be determined based on thedemodulated signals. At block 1258, an integrity of the data is verifiedbased on the determined data and the error correction code. At decisionblock 1260, it is determined if the data is verified. If the data is notverified, process 1250 proceeds to block 1262, where the data iscorrected based on the error correction code. Process 1250 may return toa calling process to perform other actions.

FIG. 13 illustrates employing multiple wireless signal paths tomultiplex an airspace within the volume of a chassis. In variousembodiments, a multiple-input and multiple-output (MIMO) process isemployed to multiplex an airspace with the volume of a chassis. Variouswireless protocols incorporate or otherwise support one or more MIMO orMIMO-like multiple signal path approaches to multiplexing an airspace.Wireless chassis portion 1300 includes one or more storage drives 1322,a corresponding wireless controller 1326, and a radio adapter 1332. Thewireless controller 1326 and the radio adapter 1332 are operative towirelessly communicate along waveguide 1334. As discussed herein, invarious embodiments, wireless controller 1326 includes a plurality ofantennas. As shown in FIG. 13, wireless controller 1326 includes twoantennas electromagnetically coupled to waveguide 1334: first antenna1340 and second antenna 1350. However, in other embodiments, a wirelesscontroller may include additional antennas. As shown in FIG. 13, thefirst antenna 1340 and the second antenna 1350 are transmittingantennas, however the first and second antennas 1340/1350 are operativeas receiving antennas also.

A channel element of radio adapter 1332, such as channel element 932 or942 of FIGS. 9A-9B, includes a plurality of antennas that areelectromagnetically coupled to waveguide 1334. In the embodiment shownin FIG. 13, the channel element includes four antennas, but otherembodiments may include more or less than four antennas. As shown inFIG. 13, the plurality of antennas of the channel element are receivingantennas, however these antennas are operative as receiving antennasalso.

The first antenna 1340 of wireless controller is shown transmitting afirst signal. The first signal if first antenna 1340 propagates alongwaveguide 1334 in multiple paths, including at least first signal path1342 and a second signal path 1344. As shown, the first signal of thefirst antenna 1340 is received by the plurality of antennas of radioadapter 1332. Likewise, the second antenna 1350 transmits a secondsignal that propagates along waveguide 1334 in multiple paths, includingat least a third signal path 1352 and fourth signal path 1354. Theplurality of antennas of radio adapter 1332 also receive the secondsignal transmitted by second antenna 1350.

When received by the plurality of receiving antennas, radio adapter 1332is operative to resolve the first signal transmitted by first antenna1340 and the second signal transmitted by second antenna 1350. Thus, theairspace with waveguide 1334 is multiplexed. Resolving the first and thesecond signals is based on at least a multiple path operator, such as amultiple path matrix. The multiple path operator is based on at leastcharacteristics of the airspace within waveguide 1334. Suchcharacteristics may include symmetrical and/or non-symmetrical featureson an interior surface of the waveguide's cavity. For instance, featuressuch as ridges, angles, shapes, folds, corrugations, or protuberancesthat are placed at symmetrical and/or non-symmetrical locations alongthe interior surface of the waveguide's channel may affect the multipathpropagation of signals with waveguide 1334, and thus the multiple pathoperator. FIG. 15A shows corrugations along the internal surface of awaveguide affecting the multiple path prorogation of signals along awaveguide.

FIG. 14 illustrates a logical flow diagram generally showing anembodiment of a process for multiplexing an airspace within a volume ofa chassis by employing a multipath propagation of wireless signalswithin a waveguide. Process 1400 may begin, after a start block, atblock 1402, where a plurality of signals are determined based on data tobe transmitted. Process 1400 proceeds to block 1404, where the pluralityof signals are wirelessly transmitted by employing a plurality oftransmitting antennas. For instance, the signals may be transmitted by awireless controller or a radio adapter along a wireless waveguide.

At block 1406, the plurality of signals are wirelessly received by aplurality of receiving antennas. For example, the plurality of signalsmay be received by one or more wireless controllers or radio adaptersthat are electromagnetically coupled to the waveguide. At block 1408,the data is determined based on the wirelessly received plurality ofsignals. Determining the data is further based on a multiple pathoperator. The multiple path operator may be employed to resolve thereceived plurality of signals, where of the signals traveled alongmultiple paths within a waveguide, as shown in at least FIG. 13.

The multipath path operator is based on the multiple paths that theplurality of signals travel within the airspace of the waveguide. Forinstance, the multiple path operator may be based on the multiple pathseach of the first wireless signal 1340 and second wireless signal 1350travel between the first and second antennas 1340/1350 and the pluralityof antennas of radio adapter 1332 of FIG. 13. Accordingly, as discussedabove, the multipath operator may be based on one or morecharacteristics of the airspace within the internal cavity of thewaveguide. Such characteristics may include uniform or non-uniformsurfaces within the cavity. In at least one embodiment, as shown in FIG.15B, the characteristics may include obstacles or wave reflectors withinthe airspace. Determining the data may be further based on noiseintroduced in the transmitting waveguide. Process 1400 may return to acalling process to perform other actions.

FIG. 15A illustrates corrugations along the internal surfaces of awaveguide which are configured and arranged to provide multipletransmission paths for wireless signals within the waveguide. Wirelesschassis portion 1500 includes similar features to wireless chassisportion 1300 of FIG. 13, including a waveguide 1534. One or moreinternal surfaces of waveguide 1534 includes a plurality of corrugations1540. As discussed throughout, and shown in FIG. 15A, such corrugationand other such structures affect the multiple path propagation ofwireless signals along waveguide 1534. Accordingly, a multiple pathoperator, such as a multipath matrix, employed to resolve the multiplesignals is based on the plurality of corrugations 1540 or other suchstructures. Corrugations 1540, or other structures, may provide enhancesresolution of the multiple signals within a waveguide, when the airspaceis multiplexed by a MIMO or MIMO-like process.

FIG. 15B illustrates structures disposed within an airspace of awaveguide which are configured and arranged to provide multipletransmission paths for wireless signals within the waveguide. Waveguide1584 of wireless chassis portion 1550 includes a plurality ofstructures, obstructions, wave reflectors, or the like, includingstructures 192, 1594, 1596, and 1598. Various embodiments may includemore or less such structures. As shown in FIG. 15B, the plurality ofstructures affect the multiple path propagation or transmission of aplurality of wireless signals within waveguide 1584. Accordingly, amultiple path operator, employed to resolve the multiple signals isbased on the plurality of such structures. Such structures may provideenhances resolution of the multiple signals within a waveguide, when theairspace is multiplexed by a MIMO or MIMO-like process. Such structuremay include any symmetric or non-symmetric cross-sectional shape. Thestructure may include electrically conductive surfaces, such that thesignals are reflected from the surfaces. Note that, as shown in FIG.15A, the plurality of radio adapter antennas are transmitting themultiple signals and the plurality of the wireless controller antennasare receiving the wireless signals. Each of the radio adapter antennasand each of the wireless controller antennas are operative to bothreceive and transmit wireless signals along multiple signal paths withinwaveguide 1584.

Exemplary Embodiment for Increasing a Bandwidth of a Wireless DataStorage Chassis

As described above, the bandwidth of a wireless chassis may be increasedmy multiplexing at least one of a frequency space, an airspace, or ageometry of the chassis. As an exemplary, but non-limiting embodiment,for increasing the bandwidth of a wireless chassis, various features ofthe 802.11ac protocols are employed and described below. The frequencyspace is multiplexed into 12 frequency channels, where each frequencychannel is 40 MHz wide and a 400 ns guard interval separates adjacentfrequency channels. Furthermore, a 256 bit Quadrature AmplitudeModulation (256-QAM) modulating scheme and a 5/6 error correction codingrate are employed. In the context of the 802.11ac protocol, an MCS indexof 9 is employed to enable the wireless communication. Each of the 12channels has a bandwidth of 200 Mbits/s/antenna. Accordingly, themultiplexed frequency space has a bandwidth of 12×200Mbits/s/antenna=2400 Mbits/s/antenna.

The geometry of the chassis is multiplexed by employing multiplewaveguides and multiple radio adapters. For instance, a cavity within awaveguide may have a corresponding bandwidth of B (depending on thefrequency multiplexing described above). When N devices arecommunicating along a single waveguide or waveguide portion, the totalbandwidth is distributed among the devices, such that the bandwidth perdevice is B/N. However, if the N devices are distributed among Mwaveguides or waveguide portions (rather than a single waveguide), thenthe bandwidth per device is M*(B/N). Accordingly, the geometry of thewireless chassis is multiplexed by distributing the communicationbetween the wireless controllers among multiple waveguides, wherein eachwaveguide is electromagnetically coupled to one or more radio adapters,as described throughout.

As also discussed throughout, the airspace within each of the multiplewaveguides may be multiplexed by employing MIMO or MIMO-like techniquesto further increase the bandwidth within the waveguide. The bandwidthmay be dynamically allocated depending on the real time operatingbandwidth requirements of the wireless chassis.

It will be understood that at least portions of the blocks of theflowchart illustrations, including at least FIGS. 11, 12A, 12B, and 14,and combinations of blocks in the flowchart illustrations, can beimplemented by computer program instructions. These program instructionsmay be provided to a processor to produce a machine, such that theinstructions, which execute on the processor, create means forimplementing the actions specified in the flowchart block or blocks. Thecomputer program instructions may be executed by a processor to cause aseries of operational steps to be performed by the processor to producea computer-implemented process such that the instructions, which executeon the processor to provide steps for implementing the actions specifiedin the flowchart block or blocks. The computer program instructions mayalso cause at least some of the operational steps shown in the blocks ofthe flowchart to be performed in parallel. Moreover, some of the stepsmay also be performed across more than one processor, such as mightarise in a multi-processor computer system. In addition, one or moreblocks or combinations of blocks in the flowchart illustration may alsobe performed concurrently with other blocks or combinations of blocks,or even in a different sequence than illustrated without departing fromthe scope or spirit of the invention.

Accordingly, blocks of the flowchart illustrations support combinationsof means for performing the specified actions, combinations of steps forperforming the specified actions and program instruction means forperforming the specified actions. It will also be understood that eachblock of the flowchart illustrations, and combinations of blocks in theflowchart illustrations, can be implemented by special purpose hardwarebased systems, which perform the specified actions or steps, orcombinations of special purpose hardware and computer instructions.

The above specification, examples, and data provide a completedescription of the manufacture and use of the composition of theinvention. Since many embodiments of the invention can be made withoutdeparting from the spirit and scope of the invention, the inventionresides in the claims hereinafter appended.

What is claimed as new and desired to be protected by Letters Patent ofthe United States is:
 1. A housing for storing a plurality of storagedrives, wherein each of the plurality of storage drives are operative tocommunicate over a network, wherein the housing comprises: one or moreradio adapters that perform one or more actions, comprisingcommunicating wireless signals in an airspace between the one or moreradio adapters and one or more wireless controllers, wherein eachstorage drive includes one or more wireless controllers; and one or moreseparate mechanical waveguides that are coupled along at least a portionof a dimension of the housing, and wherein the one or more separatemechanical waveguides include one or more internal cavities that providethe airspace for transmission of the one or more wireless signalsbetween the one or more wireless controllers and the one or more radioadapters.
 2. The housing of claim 1, wherein the one or more radioadapters include one or more wireless interfaces and one or moreexternal communication interfaces.
 3. The housing of claim 1, whereinthe one or more radio adapters perform further actions, comprising oneor more of: multiplexing frequencies of wireless signals communicated,in the airspace, between the one or more radio adapters and the one ormore wireless controllers; or multiplexing wireless signalscommunicated, in the airspace, between the one or more radio adaptersand the one or more wireless controllers based on one or morecharacteristics of the airspace.
 4. The housing of claim 1, furthercomprising one or more remote communication interfaces that providecommunication over the network with one or more remotely located networkcomputers.
 5. The housing of claim 1, further comprising one or morecharacteristics of the airspace that are based on one or morenon-uniform surfaces positioned within the one or more internalcavities.
 6. The housing of claim 1, further comprising one or more of:two or more antennas for the one or more wireless controllers to providemultipath communication of the one or more wireless signals; or two ormore antennas for the one or more radio adapters to provide multipathcommunication of the one or more wireless signals.
 7. The housing ofclaim 1, further comprising: a first waveguide that guides transmissionof the one or more wireless signals between a first portion of the oneor more wireless controllers and a first portion of the one or moreradio adapters; and a second waveguide that guides transmission of theone or more wireless signals between a second portion of the one or morewireless controllers and a second portion of the one or more radioadapters.
 8. A storage drive that communicates over a network and ispositioned in a housing, wherein the storage drive performs actionscomprising: communicating wireless signals in an airspace in the housingbetween one or more radio adapters and one or more wireless controllers,wherein each storage drive in the housing includes one or more wirelesscontrollers; and wherein the housing includes one or more separatemechanical waveguides that are coupled along at least a portion of adimension of the housing, and wherein the one or more separatemechanical waveguides include one or more internal cavities that providethe airspace for transmission of the one or more wireless signalsbetween the one or more wireless controllers and the one or more radioadapters.
 9. The storage drive of claim 8, wherein the one or more radioadapters include one or more wireless interfaces and one or moreexternal communication interfaces.
 10. The storage drive of claim 8,wherein the one or more radio adapters perform further actions,comprising one or more of: multiplexing frequencies of wireless signalscommunicated, in the airspace, between the one or more radio adaptersand the one or more wireless controllers; or multiplexing wirelesssignals communicated, in the airspace, between the one or more radioadapters and the one or more wireless controllers based on one or morecharacteristics of the airspace.
 11. The storage drive of claim 8,wherein the housing further comprises one or more remote communicationinterfaces that provide communication over the network with one or moreremotely located network computers.
 12. The storage drive of claim 8,wherein the airspace further comprises one or more characteristics ofthe airspace that are based on one or more non-uniform surfacespositioned within the one or more internal cavities.
 13. The storagedrive of claim 8, further comprising one or more of: two or moreantennas for the one or more wireless controllers to provide multipathcommunication of the one or more wireless signals; or two or moreantennas for the one or more radio adapters to provide multipathcommunication of the one or more wireless signals.
 14. The storage driveof claim 8, wherein the housing further comprises: a first waveguidethat guides transmission of the one or more wireless signals between afirst portion of the one or more wireless controllers and a firstportion of the one or more radio adapters; and a second waveguide thatguides transmission of the one or more wireless signals between a secondportion of the one or more wireless controllers and a second portion ofthe one or more radio adapters.
 15. A radio adapter that communicatesover a network and is positioned in a housing, wherein the radio adapterperforms actions comprising: communicating wireless signals in anairspace, in the housing, with one or more wireless controllers, whereineach of a plurality of storage drives in the housing include one or morewireless controllers; and wherein the housing includes one or moreseparate mechanical waveguides that are coupled along at least a portionof a dimension of the housing, and wherein the one or more separatemechanical waveguides include one or more internal cavities that providethe airspace for transmission of the one or more wireless signalsbetween the one or more wireless controllers and the radio adapter. 16.The radio adapter of claim 15, wherein the radio adapter includes one ormore wireless interfaces and one or more external communicationinterfaces.
 17. The radio adapter of claim 15, wherein the radio adapterperforms further actions, comprising one or more of: multiplexingfrequencies of wireless signals communicated in the airspace between theradio adapter and the one or more wireless controllers; or multiplexingwireless signals communicated in the airspace between the radio adapterand the one or more wireless controllers based on one or morecharacteristics of the airspace.
 18. The radio adapter of claim 15,wherein the housing further comprises one or more remote communicationinterfaces that provide communication over the network with one or moreremotely located network computers.
 19. The radio adapter of claim 15,wherein the airspace further comprises one or more characteristics ofthe airspace that are based on one or more non-uniform surfacespositioned within the one or more internal cavities.
 20. The radioadapter of claim 15, further comprising one or more of: two or moreantennas for the one or more wireless controllers to provide multipathcommunication of the one or more wireless signals; or two or moreantennas for the one or more radio adapters to provide multipathcommunication of the one or more wireless signals.